dependents/node-filing-cabinet
Get the file location associated with a dependency/partial's path
JavaScriptMIT
Issues
- 0
requirejs vulnerable to prototype pollution
#135 opened by osmithelias188 - 1
`failedLookupLocations` no longer exists in Typescript
#125 opened by odinho - 0
Use Rust / Zig implementation of enhanced resolve
#127 opened by CoenWarmer - 2
- 4
Not all imports in TypeScript are detected.
#102 opened by ThierryRietveld - 1
- 2
allow non-singleton usage
#92 opened by boneskull - 1
When `noTypeDefinitions` is enabled and the extension `.d.ts` is found, a crash can occur.
#115 opened by TotalTechGeek - 0
tsConfig argument conflates two different objects
#117 opened by vbraun - 1
Fails with an error when resolving import of the js file that has the same-named ".d.ts" type-definition file
#112 opened by williamvinogradov - 0
Resolves to wrong version
#104 opened by mredele - 2
- 3
Issue in tsConfig options resolving
#85 opened by vansosnin - 0
- 1
Resolving symlink real paths for js resolver
#81 opened by Diokuz - 3
Typescript: Support tsx files
#39 opened by mrjoelkemp - 0
- 7
Filename not given
#71 opened by Vanuan - 6
what should I do if I don't want to parse the module from node_module? for example, import * as api from 'util', 'util' is not a node_module, it is a file under the current path.
#70 opened by shawli123 - 1
- 1
- 4
- 1
configure NODE_PATH?
#62 opened by brumm - 1
Upgrade Typescript
#55 opened by GabrielCastro - 3
1.14.4 contains a breaking change
#60 opened by michaelwittig - 3
Webpack: Support Ignore Plugin
#51 opened by eoingroat - 1
- 5
- 1
- 0
CommonJS needs to resolve in directory
#2 opened by mrjoelkemp