Require statements break Browserify compatibility #875
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks for this! Why are you trying to browserify this library, by the way? |
brianc
added a commit
that referenced
this pull request
Oct 15, 2015
Require statements break Browserify compatibility
|
@brianc we were trying to get the module up & running in AWS Lambda, using the JAWS framework. JAWS uses Browserify to bundle & compress the JS files. (see serverless/serverless#201) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Using __dirname in require statements breaks compatibility with Browserify.
I've also submitted a related PR for pg-types (brianc/node-pg-types#43).