1 files changed, 0 insertions, 49 deletions
diff --git a/vanilla/node_modules/@vitest/utils/dist/constants.js b/vanilla/node_modules/@vitest/utils/dist/constants.js
deleted file mode 100644
index 385045b..0000000
--- a/vanilla/node_modules/@vitest/utils/dist/constants.js
+++ /dev/null
@@ -1,49 +0,0 @@
-// TODO: this is all copy pasted from Vite - can they expose a module that exports only constants?
-const KNOWN_ASSET_TYPES = [
-	"apng",
-	"bmp",
-	"png",
-	"jpe?g",
-	"jfif",
-	"pjpeg",
-	"pjp",
-	"gif",
-	"svg",
-	"ico",
-	"webp",
-	"avif",
-	"mp4",
-	"webm",
-	"ogg",
-	"mp3",
-	"wav",
-	"flac",
-	"aac",
-	"woff2?",
-	"eot",
-	"ttf",
-	"otf",
-	"webmanifest",
-	"pdf",
-	"txt"
-];
-const KNOWN_ASSET_RE = new RegExp(`\\.(${KNOWN_ASSET_TYPES.join("|")})$`);
-const CSS_LANGS_RE = /\.(css|less|sass|scss|styl|stylus|pcss|postcss|sss)(?:$|\?)/;
-/**
-* Prefix for resolved Ids that are not valid browser import specifiers
-*/
-const VALID_ID_PREFIX = `/@id/`;
-/**
-* Plugins that use 'virtual modules' (e.g. for helper functions), prefix the
-* module ID with `\0`, a convention from the rollup ecosystem.
-* This prevents other plugins from trying to process the id (like node resolution),
-* and core features like sourcemaps can use this info to differentiate between
-* virtual modules and regular files.
-* `\0` is not a permitted char in import URLs so we have to replace them during
-* import analysis. The id will be decoded back before entering the plugins pipeline.
-* These encoded virtual ids are also prefixed by the VALID_ID_PREFIX, so virtual
-* modules in the browser end up encoded as `/@id/__x00__{id}`
-*/
-const NULL_BYTE_PLACEHOLDER = `__x00__`;
-
-export { CSS_LANGS_RE, KNOWN_ASSET_RE, KNOWN_ASSET_TYPES, NULL_BYTE_PLACEHOLDER, VALID_ID_PREFIX };