-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for import alias #69
Comments
I don't know the exact way quibble is working internally. But it looks like the problem come from "dummyImportModuleToGetAtPath" function. When it try to "import", the original parentUrl context is lost, then package.json alias are lost too. |
Paging @giltayar for help! 🙏 |
@Poyoman39 I'll look into it. |
I'm not sure if this breaks anything, but there's a hacked out change here. It works for my case. a620990...bojavou:quibble:3e92ad3767845c8db677bd86b48dc9ab18b5bc4a It's like this: Detect private mappings which always start with node --experimental-import-meta-resolve --loader=quibble test.mjs |
Hi quibble team,
I've a feature request. On my project i'm using import alias defined in my package.json like that :
It looks like quibble loader fails at managing such import. In my .test.js file i tried to replace alias path with
await td.replaceEsm('#src/dependencies');
this lead to the following error :TypeError [ERR_PACKAGE_IMPORT_NOT_DEFINED]: Package import specifier "#src/dependencies" is not defined in package /.../node_modules/quibble/package.json imported from /.../node_modules/quibble/lib/esm-import-functions.js
Full call stack :
I remain available if you need more information
The text was updated successfully, but these errors were encountered: