Home / npm packages / optimize-css-assets-webpack-plugin
Every file of optimize-css-assets-webpack-plugin@6.0.1 as published on npm: 36 files, 18 KB. Search them by exact text or regex, in milliseconds.
It uses: process.env, the fs module.
| API | In optimize-css-assets-webpack-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. test/webpack-integration.test.js | See the lines |
| the fs module reads and writes files | Yes: 2 files e.g. test/util/helpers.js | See the lines |
| 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.
Version 6.0.1 of optimize-css-assets-webpack-plugin publishes 36 files of source, 18 KB in all, not counting images, fonts and source maps.
No: optimize-css-assets-webpack-plugin doesn't call eval() anywhere in its published files.
No: optimize-css-assets-webpack-plugin doesn't use child_process anywhere in its published files.
No: optimize-css-assets-webpack-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.