Something went wrong. Try again.
[READ-ONLY] Mirror of https://github.com/vitest-dev/vitest. Next generation testing framework powered by Vite. vitest.dev
test testing-tools vite
Something went wrong. Try again.
TypeScript
12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758// TODO: this is all copy pasted from Vite - can they expose a module that exports only constants?
export const KNOWN_ASSET_TYPES: string[] = [ // images 'apng', 'bmp', 'png', 'jpe?g', 'jfif', 'pjpeg', 'pjp', 'gif', 'svg', 'ico', 'webp', 'avif',
// media 'mp4', 'webm', 'ogg', 'mp3', 'wav', 'flac', 'aac',
// fonts 'woff2?', 'eot', 'ttf', 'otf',
// other 'webmanifest', 'pdf', 'txt',]
export const KNOWN_ASSET_RE: RegExp = new RegExp(`\\.(${KNOWN_ASSET_TYPES.join('|')})$`)export const CSS_LANGS_RE: RegExp = /\.(css|less|sass|scss|styl|stylus|pcss|postcss|sss)(?:$|\?)//** * Prefix for resolved Ids that are not valid browser import specifiers */export 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}` */export const NULL_BYTE_PLACEHOLDER = `__x00__`