-
Notifications
You must be signed in to change notification settings - Fork 640
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
[Feature Request] Resolver for NPM Modules #1175
Closed
penx opened this issue
Dec 13, 2018
· 1 comment
· Fixed by #1197 · May be fixed by dubscratch/MagicMirror#16, Matthelonianxl/create-an-issue#3 or BitcoinOutput/bsc-genesis-contractin#15
Closed
[Feature Request] Resolver for NPM Modules #1175
penx opened this issue
Dec 13, 2018
· 1 comment
· Fixed by #1197 · May be fixed by dubscratch/MagicMirror#16, Matthelonianxl/create-an-issue#3 or BitcoinOutput/bsc-genesis-contractin#15
Labels
Comments
A possible solution would be to use the same convention as in some scss projects, in that starting a path with
|
fdintino
added a commit
that referenced
this issue
Mar 5, 2019
fdintino
added a commit
that referenced
this issue
Mar 5, 2019
fdintino
added a commit
that referenced
this issue
Mar 5, 2019
fdintino
added a commit
that referenced
this issue
Mar 5, 2019
fdintino
added a commit
that referenced
this issue
Mar 5, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This has previously been raised as #1136 but is still an issue.
As previously raised:
A potential solution has previously been suggested:
However, as far as I know, this doesn't use standard node_modules resolution and so would not work under several conditions:
npm link
The text was updated successfully, but these errors were encountered: