Home / npm packages / source-map-js
Every file of source-map-js@1.2.2 as published on npm: 18 files, 143 KB. Search them by exact text or regex, in milliseconds.
It uses: new Function().
| API | In source-map-js | |
|---|---|---|
| eval() runs a string as JavaScript | No | Who does |
| new Function() builds a function from a string, like eval (with or without new) | Yes: 1 file e.g. lib/quick-sort.js | See the lines |
| 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/source-map-consumer.js | 44 KB |
README.md | 26 KB |
lib/util.js | 15 KB |
lib/source-map-generator.js | 15 KB |
lib/source-node.js | 14 KB |
lib/base64-vlq.js | 4.7 KB |
lib/binary-search.js | 4.2 KB |
lib/quick-sort.js | 4.2 KB |
source-map.d.ts | 3.4 KB |
lib/array-set.js | 3.2 KB |
package.json | 2.5 KB |
lib/mapping-list.js | 2.3 KB |
lib/base64.js | 1.5 KB |
LICENSE | 1.5 KB |
source-map.js | 405 B |
lib/source-map-generator.d.ts | 41 B |
lib/source-map-consumer.d.ts | 40 B |
lib/source-node.d.ts | 33 B |
Version 1.2.2 of source-map-js publishes 18 files of source, 143 KB in all, not counting images, fonts and source maps.
No: source-map-js doesn't call eval() anywhere in its published files.
No: source-map-js doesn't use child_process anywhere in its published files.
No: source-map-js 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.