Home / npm packages / babel-eslint
Every file of babel-eslint@10.1.0 as published on npm: 16 files, 30 KB. Search them by exact text or regex, in milliseconds.
It uses: none of the APIs we check for.
| API | In babel-eslint | |
|---|---|---|
| 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 | No | Who does |
| 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 |
|---|---|
lib/analyze-scope.js | 8.9 KB |
README.md | 4.3 KB |
lib/babylon-to-espree/toAST.js | 2.7 KB |
lib/parse.js | 2.5 KB |
lib/babylon-to-espree/toToken.js | 2.4 KB |
lib/babylon-to-espree/attachComments.js | 2.1 KB |
lib/babylon-to-espree/convertTemplateType.js | 1.8 KB |
package.json | 1.7 KB |
LICENSE | 1.1 KB |
lib/babylon-to-espree/index.js | 779 B |
lib/index.js | 545 B |
lib/babylon-to-espree/convertComments.js | 472 B |
lib/visitor-keys.js | 415 B |
lib/parse-with-scope.js | 325 B |
lib/babylon-to-espree/toTokens.js | 311 B |
lib/require-from-eslint.js | 233 B |
Version 10.1.0 of babel-eslint publishes 16 files of source, 30 KB in all, not counting images, fonts and source maps.
No: babel-eslint doesn't call eval() anywhere in its published files.
No: babel-eslint doesn't use child_process anywhere in its published files.
No: babel-eslint 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.