You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure if it's a Node.js or jest-resolve issue, so I'm cross-posting it.
🐛 Bug Report
At Node.js packages docs it says it's possible to self-reference and import a package from it's own modules by using the package name, the same was as it's done with dependencies installed on node_modules. I'm self-referencing my package itself in my jest tests, it says it can't find it:
Since my package has a scope (package name is in the form with @<scope>/<packageName>) and there's no examples or references in Node.js docs about self-referencing scoped packages, maybe this is a Node.js packages resolving algorythm.
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.
Not sure if it's a Node.js or
jest-resolve
issue, so I'm cross-posting it.🐛 Bug Report
At Node.js packages docs it says it's possible to self-reference and import a package from it's own modules by using the package name, the same was as it's done with dependencies installed on
node_modules
. I'm self-referencing my package itself in myjest
tests, it says it can't find it:Since my package has a scope (package name is in the form with
@<scope>/<packageName>
) and there's no examples or references in Node.js docs about self-referencing scoped packages, maybe this is a Node.js packages resolving algorythm.To Reproduce
Steps to reproduce the behavior:
Expected behavior
The self-referenced package should be imported.
Link to repl or repo (highly encouraged)
envinfo
The text was updated successfully, but these errors were encountered: