Skip to content

Tags: bminer/module-concat

Tags

v2.3.0

Toggle v2.3.0's commit message
Added `path` parameter to each compiler Updated docs Push to 2.3.0

v2.2.0

Toggle v2.2.0's commit message
Provide slightly more support for `browser` field in package.json Added relevant documentation Push to 2.2.0

v2.1.4

Toggle v2.1.4's commit message
We now estimate the resolved module path before resolving using node-… …resolve to	see if the resolved path matches any file in `options.excludeFiles`;	previously, it was a lot more likely that missing files in the	`excludeFiles` array would throw an error Push to 2.1.4

v2.1.2

Toggle v2.1.2's commit message
Fixed a couple minor bugs - `this` in a module's context is not the module function anymore; instead, it	is just the global `this` context - `browser` field in package.json can be an Object; this is currently	unsupported when bundling a browser module, but at least now it will be	ignored when determining the entry point of a module. Only a string value	is supported. Push to 2.1.2

v2.1.1

Toggle v2.1.1's commit message
Project name changed from `node-module-concat` to `module-concat` Fixed minor issue when resolving entry module path Push to 2.1.1

v2.1.0

Toggle v2.1.0's commit message
Now defaults to throwing an Error when a required module is not found `options.excludeNodeModules` can now be set to `true` or to an Array containing	modules to be excluded from the project `options.allowUnresolvedModules` can now be set to `true` to ignore modules that	could not be found. `stats.unresolvedModules` contains information about modules that could not be	found. Only relevant when `options.allowUnresolvedModules` is `true`. Better normalization of `options` in stream constructor Push to 2.1.0

v2.0.0

Toggle v2.0.0's commit message
Added `options.extensions` and `options.compilers` `options` are now passed along to `resolve` module Updated README documentation to explain `extensions` and `compilers` options Added CHANGELOG Push to 2.0.0

v2.0.0-beta

Toggle v2.0.0-beta's commit message
Almost a complete re-write. Now supports streaming the project output! Breaking API changes:	- Replaced `options.includeNodeModules` with `options.excludeNodeModules`	(defaults to including modules from node_modules)	- `options.outputFile` is now optional when using the stream API	- `cb` is of the form `cb(err, stats)` where `stats` is an Object	containing `files` and `addonsExcluded` properties. (see README)	- Added Readable stream API	- Dropped support for Node < 4 Depends on `resolve` module instead of using a hack for `require.resolve` Now supports `browser` flag to concatenate a project for the browser. This	feature reads the `browser` field instead of the `main` field in the	`package.json` file of an included module to determine which file to	include in the build. Updated README doc. Updated test_project Fixed a bug in `header.js` so that `require.main` is properly set Push to 2.0.0-beta

v1.5.0

Toggle v1.5.0's commit message
Fixed header and footer to be browser-compatible Push to 1.5.0

v1.4.0

Toggle v1.4.0's commit message
Native modules are no longer included in `outputFile` Callback now includes `nativeModules` Array, which includes paths to native	modules that were detected (but not included) while scanning the project Added `includeNodeModules` option to allow any code in node_modules to be	included in the project Resulting `outputFile` has some line comments removed Fixed up some regex to scan for `require(...)` expressions Added support for `module.parent` Updated README documentation Push to 1.4.0