-
-
Notifications
You must be signed in to change notification settings - Fork 6.4k
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
Can't self-reference a scoped package using its name #11161
Labels
Comments
Node.js issue at nodejs/node#37618 |
Duplicate of #10883 |
Thank you for the reference :-) |
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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: