browserify support?
See original GitHub issueThis lib is written with ES6, so it doesn’t get parsed correctly with browserify:
Parse error at -:3082,12
SyntaxError: Unexpected token: name (x)
Error
It’d be great if there were a browser version available to serve as a polyfill for IE.
Issue Analytics
- State:
- Created 7 years ago
- Comments:30 (27 by maintainers)
Top Results From Across the Web
Browserify
Browserify lets you require('modules') in the browser by bundling up all of your dependencies. Install Documentation · Source Code · Help + Articles...
Read more >browserify/browserify: browser-side require() the node.js way
Use a node-style require() to organize your browser code and load modules installed by npm. browserify will recursively analyze all the require() calls...
Read more >Browserify
Start using browserify in your project by running `npm i browserify`. There are 3187 other projects in the npm registry using browserify.
Read more >Lesson 3. Bundling modules with Browserify
Many programming languages support modularized code. Ruby calls these pieces of modularized code gems, Python calls them eggs, and Java calls them packages....
Read more >Publishing your first Browserify/Node module
In this article we will go with Browserify. To install Browserify open a terminal and type: npm install -g browserify. Hello Browserify. To...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
You can’t be spec compliant without tr46, so you’ll have to come to some kind of trade-off here.
I would use it in an isomorphic router to get a url pathname, and query from a string to match against. I found this issue because I was looking for a solution to that actually.
Right now a check for
window && (URL || createFromLInk) || module && module.exports && (require('url')).URL || myCustomURLConstructor
is how I’m doing it. Which at least works for the time being.