-
Notifications
You must be signed in to change notification settings - Fork 2k
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
fix(CLI): get rid of Browserify absolute path workaround #1449
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems to be an awful lot of changes to npm-shrinkwrap.json
- are they definitely all wanted / needed / desired?
# module errors when executing it in another computer. | ||
# The fix is to replace absolute paths with `__dirname` | ||
node <<EOF > "$ARGV_OUTPUT.TMP" | ||
const separator = process.platform === 'win32' ? '\\\\\\\\\\\\\\\\' : '\\/'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yay, bye bye megabackslashosaurus :-)
@lurch We had an older browserify version listed as a development dependency. My fork is running the latest one, which triggered some updated dependencies :) |
Do you need to update this PR to point to the new changes you made on browserify/browserify#1725 ? EDIT: To clarify my question...
but in
and https://github.com/jviotti/node-browserify/commit/6ea4c1bd395e86a754131d547c29cc9dffd05b38 is a commit from before the most recent fix on that branch https://github.com/jviotti/node-browserify/commit/14691ac9257063000e4aa216073cdad28b9d04e1 |
We encountered a Browserify bug when releasing the CLI, where absolute paths would be hard-coded in the final bundle. Since we were in the middle of a release process, we added a quick and dirty search-and-replace workaround on `concatenate-javascript.sh`. After the release, we submitted a PR to Browserify which fixes the issue. This commit makes use of my personal fork to be able to use such fix while it gets merged to the main project. See: browserify/browserify#1725 See: #1409 Fixes: #1429 Signed-off-by: Juan Cruz Viotti <jviotti@openmailbox.org>
Fixed! |
23e5a0a
to
0179813
Compare
We encountered a Browserify bug when releasing the CLI, where absolute
paths would be hard-coded in the final bundle. Since we were in the
middle of a release process, we added a quick and dirty
search-and-replace workaround on
concatenate-javascript.sh
.After the release, we submitted a PR to Browserify which fixes the
issue. This commit makes use of my personal fork to be able to use such
fix while it gets merged to the main project.
See: browserify/browserify#1725
See: #1409
Fixes: #1429
Signed-off-by: Juan Cruz Viotti jviotti@openmailbox.org