browserify

I am new to the whole browserify thing. I have been trying to use browserify + reactify + gulp to transform, minify and combine a React application. As long as I have a single React.createClass with a single module.exports = MyComponent everything works fine. Since I have several shared components I physically host in the same file and reuse across projects, I would like to export more than one component. I have tried an array: module.exports = [Component1, Component2] and have also tried an object with multiple properties: module.exports = {Comp1: Componenet1, Comp2: Component2} and have also

This is tad long but I'll need the code example to illustrate my confusion. After which I am interested to the answer for the following: How do I use require('module') instead of require('../../src/module') or require('./module') ? How do I reuse ./index.js in spec/specs.js without duplicating work? (And preventing src/app.js from running as it's an entry module). I've started several browser based projects already and love browserify and grunt. But each project dies at the same point in my development/learning curve. Once I add testing to the mix and have to manage two browserify bundles (

Just started to use browserify , but I cannot find documentation for how to get it spilling out minified output. So I am looking something like: $> browserify main.js > bundle.js --minified topek Pipe it through uglifyjs: browserify main.js | uglifyjs > bundle.js You can install it using npm like so: npm install -g uglify-js As of 3.38.x you can use my minifyify plugin to minify your bundle and still have usable sourcemaps. This is not possible with the other solutions -- the best you can do is map back to the uncompressed bundle. Minifyify maps all the way back to your separate source files

const gulp = require('gulp'); const $ = require('gulp-load-plugins')(); const source = require('vinyl-source-stream'); const browserify = require('browserify'); gulp.task('build', () => browserify('./src/app.js').bundle() .pipe(source('app.js')) .pipe(gulp.dest('./build')) // OK. app.js is saved. .pipe($.rename('app.min.js')) .pipe($.streamify($.uglify()) .pipe(gulp.dest('./build')) // Fail. app.min.js is not saved. ); Piping to multiple destinations when file.contents is a stream is not currently supported. What is a workaround for this problem? Currently you have to use two streams for each

I'm trying to write a gulp task allowing me to use modules in JS (CommonJS is fine), using browserify + 6to5. I also want source mapping to work. So: 1. I write modules using ES6 syntax. 2. 6to5 transpiles these modules into CommonJS (or other) syntax. 3. Browserify bundles the modules. 4. Source maps refers back to the original ES6 files. How to write such a task? Edit: Here's what I have so far: gulp task gulp.task('browserify', function() { var source = require('vinyl-source-stream'); var browserify = require('browserify'); var to5ify = require('6to5ify'); browserify({ debug: true })

I'm using browserify-shim and I want to use a generic jQuery plugin. I have looked over the Browserify-shim docs multiple times and I just can't seem to understand what's going on and/or how it knows where to put plugins, attach to the jQuery object etc. Here's what my package.json file looks like: "browser": { "jquery": "./src/js/vendor/jquery.js", "caret": "./src/js/vendor/jquery.caret.js" }, "browserify-shim": { "caret": { "depends": ["jquery:$"] } } According the the example given on the browserify-shim documentation, I don't want to specify an exports because this plugin (and most if not

I want to use a library that was build using browserify. The library built correctly and works fine when it is used by itself. Now that built library is in my vendors/ directory, and I try to require it in my new application: var myLib = require('./vendors/myLib'); When I try to browserify my application, it complains that it can't find some of the internal require statements inside that library: Error: Cannot find module '../utils/logger' from '/myApp/vendor' Browserify seems to be trying to re-build the lib from the wrong directory. How can I fix this? More specifics: The lib looks like this