asset-smasher - npm Package Versions

0.3.2 (June 20, 2013)

• Check that found 'asset' is not a non-manifest directory. (Fixes #18)

0.3.1 (June 20, 2013)

Enhanced AMD support

• Make AMD support opt-in - must specify 'amd: true', or 'amd: {....}' in asset-smasher config
• Allow a 'baseLogicalPath' option to be in the amd option object that will be stripped off the front of all module ids (useful for shortening module names if for example, they are all inside a 'js' folder in their logical path
• Give anonymous/simple commonjs wrapped define calls module ids (and dependency arrays for simple commonjs wrapper)

0.3.0 (June 1, 2013)

Functional Changes

• The JSX transformer now can transform .js files (without the additional .jsx extension) as long as the /** @jsx React.DOM */ comment is present in the file.
• For .jsx files, the JSX transformer will add the /** @jsx React.DOM */ comment to the file if it is missing.
• CommonJS-style .js files can now be automatically wrapped with AMD define calls if a /** @amd */ comment is present in the file. See the "AMD Support" section of the README for more info.

API Changes (this should only affect you if you've written custom transformers)

• The shouldTransform and transformedFileName methods in transformers now receive the asset object as a second parameter
• The asset object now has a transformInfo property (that is an object) that transformers can use to put information in when they are processing. This can be used, for example, to prevent a file from being processed more than once (see jsx_transform.js for an example)
• Post-transform operations now must be a constructor function rather than just a function(asset, cb). This is to allow options to be passed into the post-transformer (see end_js_semicolon.js or the new amd_wrapper.js for examples)

0.2.12 (May 30, 2013)

• Add a .jsx transformer for use with React

0.2.11 (May 18, 2013)

• No functional changes
• Extract and use dependency-graph module.

0.2.10 (April 29, 2013)

• Ensure assets required by a manifest are of the right type. (Fixes #15)

0.2.9 (April 29, 2013)

• Ignore require_dir directive in manifest file if the required directory doesn't exist. Previously this would throw an EMFILE and was inconsistent with what require and require_tree did (which was ignore the directive). (Fixes #13)
• Add two additional options, --verbose and --noclean. --verbose will log information about what's going on to the console, while --noclean will not delete the output directory when running the tool (by default the output directory will be cleared). (Fixes #13)

0.2.8 (April 28, 2013)

• Allow 'manifest directories' to be created. If a directory name ends in '.mf' it is treated as it it were a manfiest file that does a require_tree on that directory. (Fixes #12)

0.2.7 (April 17, 2013)

• Use async.eachLimit to avoid EMFILE in asset output. (Fixes #10)

0.2.6 (April 17, 2013)

• Limit the number of files to process in parallel to avoid EMFILE. (Fixes #9)