-
-
Notifications
You must be signed in to change notification settings - Fork 133
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
Error when bundling resources from outside node_modules #567
Labels
Comments
both bugs confirmed |
This was referenced Mar 30, 2017
JeroenVinke
added a commit
to JeroenVinke/cli
that referenced
this issue
Mar 30, 2017
This was referenced Mar 30, 2017
Merged
JeroenVinke
added a commit
to JeroenVinke/cli
that referenced
this issue
Apr 7, 2017
JeroenVinke
added a commit
to JeroenVinke/cli
that referenced
this issue
Apr 8, 2017
JeroenVinke
added a commit
to JeroenVinke/cli
that referenced
this issue
Apr 17, 2017
JeroenVinke
added a commit
to JeroenVinke/cli
that referenced
this issue
Apr 30, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm submitting a bug report
Library Version:
0.27.0
Operating System:
Windows 10
Node Version:
v6.9.5
NPM Version:
3.10.9
Browser:
all
Language:
ESNext
Current behavior:
node_modules
folder I get an error fromaurelia-templating-resources
.step to reproduce
To showcast the problem, I created a new project and installed
jquery
via npm.I added it to the bundle like this:
and everything worked fine
then I took the
jquery
directory out ofnode_mdules
and put it into a directory calledexternal_modules
(this directory is a brother to thenode_modules
directory ).I changed my bundle config accordingly to:
and I get this error when building:
also, if I try to bundle a library that dont come from npm (a private library called
keylines
that I can't show here because of legal reasons).the library is amd compatible, and even if i put the library code inside the
node_modules
folder - the bundler complaines aboutpackage.json
file missing.The text was updated successfully, but these errors were encountered: