-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
filter build directory from browserify output #149
Conversation
See cdnjs/cdnjs#3039 cdnjs/cdnjs#3043 for why this is helpful.
If you use a recent version of browserify, you shouldn't have paths. |
Is 3.44.2 not recent? |
I just ran the command here, and there's no build output path. Browserify replaced them with index numbers several months ago |
I just did an (edit: if I've somehow got something screwed up on my end, would love to know what/how to fix, I'm not super familiar with node) |
Please update the dependencies and the script command like I stated on your other PR.
|
That does not work for me.
|
Asking substack to figure out what we're doing wrong. |
one sec, forgot to update the dependencies, trying that. Update: nope, that wasn't it. Just updated the dependency, did |
Is there maybe a config file somewhere that's changing the behavior? http://stackoverflow.com/questions/21993073/browserify-with-paths-to-folders-in-my-system |
According to substack, the issue might be due to dependency resolution. If one dependency resolves to a path different than the rest, Can you run without the uglify step and paste each match here? I did a clean git, npm install, and ran |
Actually, can you search for each instance of |
How about this?
|
The fact that @ryancdotorg has some of the arguments to EDIT (2): EDIT: |
possibility fixed with browserify/insert-module-globals#31 |
@pyramids edit number 2 seems to describe the issue. |
@terinjokes yeah, my mistake, you described it well before but I guess I only started to understand whilst editing. Thanks. |
this seems to actually be caused by a bug in browserify, so closing. |
See
cdnjs/cdnjs#3039 cdnjs/cdnjs#3043
for why this is helpful.