Support for plugins (#207)
BREAKING – options.transform, options.load, options.resolveId, options.resolveExternal and options.external are no longer supported, and should be handled by plugins. More info
BREAKING – the .js extension is only added if it looks like there's no extension, allowing e.g. import data from 'data.json' (with the appropriate transformer). For safety, always include the file extension – import ./foo.js, not ./foo

0.19.2

published 0.19.2 • 9 years ago

Changelog

Fix exporting namespaces to include all of their exports (#204)
Namespace exotic objects are frozen to ensure that its properties cannot be modified, reconfigured, redefined or deleted (#203)
Fix ReferenceError: Promise is not defined in node v0.10 (#189)

0.19.1

published 0.19.1 • 9 years ago

Changelog

published 0.19.0 • 9 years ago

Changelog

breaking The transform option is no longer passed through to custom loaders. Loaders should only concern themselves with providing source code; transformation will always take place
options.transform functions can return a string, or a {code, map, ast} object. Where possible, sourcemap chains will be flattened (#175)
options.resolveId, options.resolveExternal and options.load can each be a function or an array of functions. If an array, the first non-null/undefined return value is used. In both cases, failed resolution/loading will fall back to the defaults, unless an error is thrown. (#174)
New intro and outro options – similar to banner and footer except inserted inside any format-specific wrapper
Multiple var declarations in an export block (e.g. export let a = 1, b = 2) are split up to facilitate tree-shaking (#171)
More informative error when using a missing namespace property (#169)
Update various dependencies