Comments (4)
mrjoelkemp
commented on July 17, 2024
I was hacking together support without a lot of time for the effort. There must be a better way. Would be great to avoid sniffing the module type (es6, amd, cjs) to determine the proper configuration. Is there an es6 config value that would suffice? I imagine non-es6 module types are unlikely to use this lib; we can always add the module type sniff (making sure to reuse asts) if need be.
from node-filing-cabinet.
amitdahan
commented on July 17, 2024
+1 for module type sniff
from node-filing-cabinet.
claudineioj
commented on July 17, 2024
@mrjoelkemp any idea on when it might be released?
It didn't work properly on my typescript files since I use a webpack alias in my imports.
from node-filing-cabinet.
mrjoelkemp
commented on July 17, 2024
Thanks for following up. I haven't looked into it since the issue was created. I'm open to a PR that fixes the issue. Any help is appreciated.
from node-filing-cabinet.
Related Issues (20)
- Not all imports in TypeScript are detected. HOT 4
- Resolves to wrong version
- Fails with an error when resolving import of the js file that has the same-named ".d.ts" type-definition file HOT 1
- When `noTypeDefinitions` is enabled and the extension `.d.ts` is found, a crash can occur. HOT 1
- tsConfig argument conflates two different objects
- `failedLookupLocations` no longer exists in Typescript HOT 1
- Use Rust / Zig implementation of enhanced resolve
- configure NODE_PATH? HOT 1
- Allow alternative fs to be used for reading files. HOT 1
- Tests assertions fail on windows under vscode due to / versus \ in paths. HOT 1
- 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. HOT 6
- Filename not given HOT 7
- Typescript module resolution does not resolve arbitrary file extensions
- Resolving symlink real paths for js resolver HOT 1
- Consider supporting Webpack configurations that export a Promise
- Issue in tsConfig options resolving HOT 3
- Allow multiple default lookups for projects with JS and TS usage HOT 2
- returns empty path for require'd json file w/ no extension HOT 1
- allow non-singleton usage HOT 2
- webpack config appears to be re-executed once for every resolve attempt HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from node-filing-cabinet.