browserify icon indicating copy to clipboard operation
browserify copied to clipboard

browser-side require() the node.js way

Results 129 browserify issues
Sort by recently updated
recently updated
newest added

Hello. I'm doing a Outlook Add-in and found the Browserify module on my search to use the require to the 'mssql' NPM module. My job is to do a selectbox...

This is my subjective opinion and I might as well be wrong, but I really don't like option names like "debug". - it says little/nothing about actual effect - it...

feature-request
patch-welcome

This might be a long shot but I'd like to see this in browserify. The ES6 module syntax has a few nice features compared to commonJS `require` method, namely [bindings](https://github.com/esperantojs/esperanto/wiki/Bindings)...

feature-request

I have a shared module called `foo` that I include in my project's node_modules directory via npm link. In the `foo` module, I have a `require('react')` statement where 'react' is...

I'm hashing the bundle contents for cache busting purposes but the bundle output changes even when there are no changes to the source files. Sounds like this was previously addressed...

bug

Use the latest punycode, since punycode(1.3.2) export with: `define('punycode', function() { return punycode; }); ` which isn't portable when using requireJS.

the URL module is built in in node, but when you have browserify in you stack that means nodejs great url module is replaced but non compatible trash making life...

I'm creating a three.js loader, but there's a lot of sweet stuff from npm which I'd really like to leverage. Since I want as few dependencies as possible it would...

In Windows, Source mapping contain a backslash and not a forward slash. This causes Chrome to think the whole path is the file name.

windows

Here's a minimal example demonstrating the problem: https://gist.github.com/nathan/6fc02adb0745e71f51836a374dcf1011 Essentially, a `browser` field which maps from a filename with an extension to a filename without an extension (e.g., `"./default.js": "./browser"`) breaks...

bug