jspm 0.15.0
Breaking Changes
jspm endpoint config github
is nowjspm registry config github
. The idea being to cut down on unnecessary terminology by using the term registry or registry endpoint over endpoint. See #589. I understand this isn't ideal for backwards-compatibility, so feedback welcome if this is too much of a tricky change to make.- Babel and Traceur are now installed as devDependencies and loaded as modules themselves.
- Bundles are now fully-normalized so that map config in production is only needed for dynamic loading or normalization.
Features
bundle-sfx
now automatically includes Traceur or Babel runtime as needed (#576)- Babel now uses the runtime transformer loading only the necessary runtime modules as needed (#535)
- Direct
var builder = new require('jspm').Builder()
API to get SystemJS builder instance (#412) - Wildcard bundling arithmetic support (#404). See SystemJS builder release notes for more info https://github.com/systemjs/builder/releases/tag/0.10.0.
- Overrides now persist in the package.json
overrides
property (#398) jspm cache-clear
command thanks to @subesokun (d9c2d18)- New
--quick
install option to skip hash validations (#376) devDependencies
are now supported in the package.json (jspm install --dev
) (#115)- Arithmetic support for sfx bundles (#601)
jspm link
will now read version, registry and name from the package.json by default. It is also possible to link into thejspm
registry allowing forjspm install --link jquery@linked
- Packages published on npm can have the
jspmNodeConversion
property set to false to opt-out of all conversion operations.
Bug Fixes
- Case where
registry: 'jspm'
was being ignore unnecessarily (#559) - Fine-grained adjustments to package.json property clobbering with tests (#561, d44511b)
- Windows path fixes (#563)
- Fix install error when
lib
is set to.
(#583)
Many thanks to @theefer, @devmondo, @hgl and @subesokun for help finding bugs in the beta release.