Home / npm packages / mini-css-extract-plugin
Every file of mini-css-extract-plugin@2.10.2 as published on npm: 16 files, 140 KB. Search them by exact text or regex, in milliseconds.
It uses: process.env.
| API | In mini-css-extract-plugin | |
|---|---|---|
| eval() runs a string as JavaScript | No | Who does |
| new Function() builds a function from a string, like eval (with or without new) | No | Who does |
| child_process starts other programs | No | Who does |
| process.env reads environment variables | Yes: 1 file e.g. README.md | See the lines |
| the fs module reads and writes files | No | Who does |
| http / https makes or serves HTTP requests with Node's own modules | No | Who does |
| fetch() makes HTTP requests | No | Who does |
| XMLHttpRequest makes HTTP requests the old browser way | No | Who does |
| crypto hashes, encrypts or makes random numbers | No | Who does |
| WebAssembly loads WebAssembly code | No | Who does |
| document.cookie reads or writes browser cookies | No | Who does |
| install scripts runs a script when it's installed | No | Who does |
Exact matches in the published files, so a mention in a comment counts too: open the lines to check.
| File | Size |
|---|---|
dist/index.js | 47 KB |
README.md | 32 KB |
dist/loader.js | 15 KB |
dist/utils.js | 13 KB |
types/index.d.ts | 11 KB |
dist/hmr/hotModuleReplacement.js | 6.0 KB |
package.json | 3.3 KB |
types/loader.d.ts | 3.1 KB |
dist/plugin-options.json | 2.6 KB |
types/utils.d.ts | 2.6 KB |
dist/loader-options.json | 1.3 KB |
dist/hmr/normalize-url.js | 1.1 KB |
LICENSE | 1.1 KB |
types/hooks.d.ts | 430 B |
types/hmr/hotModuleReplacement.d.ts | 374 B |
types/hmr/normalize-url.d.ts | 73 B |
Version 2.10.2 of mini-css-extract-plugin publishes 16 files of source, 140 KB in all, not counting images, fonts and source maps.
No: mini-css-extract-plugin doesn't call eval() anywhere in its published files.
No: mini-css-extract-plugin doesn't use child_process anywhere in its published files.
No: mini-css-extract-plugin has no preinstall, install or postinstall script in its package.json.
The same engine answers over your documents and repositories: exact text and regex, every match counted, from your code or your AI agent.