We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
not public
npm
Windows
the one that comes with nextjs 14.2.3
In webpack we define alias for webpack
config.resolve.alias['@eavfw/utils'] = path.resolve(__dirname, '../../node_modules/@eavfw/utils');
the module is there, and i suspect this being related to that the package is linked in with npm (basically a symlink)
but building causes nextjs app with turbo not to resolve it.
We expect it to load packages even if linked with npm like webpack is doing :)
use npm link and try alias to the module
No response
The text was updated successfully, but these errors were encountered:
Please open an issue on the next.js repo https://github.com/vercel/next.js/issues/new?assignees=&labels=template%3A+bug&projects=&template=1.bug_report.yml
Sorry, something went wrong.
No branches or pull requests
Verify canary release
Link to code that reproduces this issue
not public
What package manager are you using / does the bug impact?
npm
What operating system are you using?
Windows
Which canary version will you have in your reproduction?
the one that comes with nextjs 14.2.3
Describe the Bug
In webpack we define alias for webpack
the module is there, and i suspect this being related to that the package is linked in with npm (basically a symlink)
but building causes nextjs app with turbo not to resolve it.
Expected Behavior
We expect it to load packages even if linked with npm like webpack is doing :)
To Reproduce
use npm link and try alias to the module
Additional context
No response
The text was updated successfully, but these errors were encountered: