Releases: jspm/jspm-cli
jspm 0.10.1
jspm CLI features
- Endpoint API v2 post-install dependencies feature to allow Node core libs downloaded only when used (c5125f1)
- Upgrade path to [email protected] (0ef24c6)
- Simplify logging by silencing fresh secondary installs (3c29780)
- Show a warning for packages without a main (2d5c923)
- Support a
basepath
argument for jspm init - egjspm init .
(a8123fd, a168862) - Show a warning for packages with heavy processing requirements (5c1d144)
jspm CLI bug fixes
- When setting
registry: "npm"
for a GitHub repo, process configuration with npm endpoint (ebbd8f2) - Remove legacy jspm CLI 0.6 global support (b4a1f5f)
- Fix uninstall behaviour (8e39b25)
jspm npm features
- Support all Node core libs only when needed on both browser and server (jspm/npm@6a15e96, jspm/npm@3645f82, jspm/npm@d0b37ff)
- Support
browserify
field (jspm/npm@d30d6c3)
jspm npm bug fixes
- Gracefully handle cache corruptions (jspm/npm@77945d7)
jspm 0.10.0
Updates to ES6 Module Loader 0.11, SystemJS 0.11 and Traceur 0.0.79 (see links for loader release notes).
Also updates the Endpoint API to 1.1.
Breaking Changes
- The path rule
System.paths['app/*'] = 'lib/*'
is now always created whereapp
is the current project package name, andlib
is thedirectories.lib
value or default (a7c61e9). - GitHub repos can now be treated as npm repos by setting
registry: npm
in their package.json (#217)
New Features
jspm init --prompts
option to run through package setting prompts (277aed6)require('jspm').uninstall
added to API (690c3ea)require('jspm').import
allows loading modules in Node with nodelibs support (6dd4277)- Compatibility changes to allow npm scoped packages (5ba2c65)
- npm and GitHub endpoints now provide auth testing workflows
Enhancements
- A confirmation log message is shown on install for trees without forks (512bb81)
- Endpoint hook errors are now package-specific (596db44)
- Loader files are always downloaded on init (730b64c)
- Loader files are globally cached (4baa172)
jspm -v
is now less verbose (4dd5974)
Bug Fixes
jspm 0.9.0
Highlighted Features:
- Full source maps and minification for bundles with
jspm bundle app/main -m
. - Injected bundles can be removed easily with
jspm unbundle
. config.js
now contains exact version resolutions only, upgrades will occur gracefully, but the config file is not backwards-compatible with former jspm versions so be careful committingconfig.js
when upgrading.jspm install
will now act as a reproducible install, like npm shrinkwrap, and will never alter the existing config resolutions.jspm install jquery --lock
will act as a stable install, not altering any existing config resolutions.jspm install npm:underscore
will install into the nameunderscore
by default - this is to discourage code containing requires likerequire('npm:underscore')
and ensure all requires are always portable.jspm update
will update all dependencies as defined in the package.jsonjspm clean
will remove orhpaned dependencies, and clear ununsed packages fromjspm_packages
.jspm uninstall
updated to applyjspm clean
by default.jspm inspect
will show a nice list of all packages and versions.jspm inspect --forks
will show the current forks.jspm inspect github:some/package
will show the version resolution constraints for a given package.jspm link
andjspm install --link
have been refined and optimized.jspm run moduleName
can be used to execute on the server,jspm install nodelibs
supports NodeJS server libs withimport fs from 'nodelibs/fs
.
A massive thanks to the Client Platform team at Workiva for sponsoring these key features for this release.
Credit to @crisptrutski for help with source maps, @OliverJAsh for pushing for server support and @subesokun for help testing the linking workflow.
For the full change PR, see from the interface changes https://github.com/jspm/jspm-cli/pull/240/files#diff-2cce40143051e25f811b56c79d619bf5L45.
The resolution algorithm itself now has much better handling of version fork resolutions. The code is relatively well commented, and can be read from around https://github.com/jspm/jspm-cli/blob/master/lib/install.js#L110.
jspm 0.8.5
Features
- New ES6 Module Loader release (https://github.com/ModuleLoader/es6-module-loader/releases/tag/v0.10.0)
- New SystemJS release (https://github.com/systemjs/systemjs/releases/tag/0.10.0)
- Normalize resolver provided through jspm API (650400a)
- Format-specific mains allowing inter-package cycles to behave correctly for the module format (7a25d33)
- Experimental
endpoint export
method (d12fbba) - Dedupe package.json
jspm
property against base package.json (7ee062f, #239)
Bug Fixes
jspm 0.8.4
- Fix undefined format shim (3e8817d)
jspm 0.8.3
- Fix format shimming bug (b68942a)
jspm 0.8.2
jspm 0.8.1
- Update Traceur and fix global config saving (c6665bf)
jspm 0.8.0
- Various windows fixes (2db47cb)
- Use node-liftoff to enable local installs of jspm optionally (80beb52)
- Support
directories.baseURL
- Allow file overrides
jspm install package -o file.json
(72120cc) - Include loader file source maps (17ba71d)
- Endpoint API updates, see https://github.com/jspm/jspm-cli/wiki/Endpoint-API
- Set precedence of branch versions (e5e34f8)
- Update version algorithms to match node-semver 4 (5972ae4)
- Separate npm build operations entirely from jspm core (88003ea)
- Separate the jspm registry into a separate project allowing the registry URL to be customized through -
jspm endpoint config jspm
(0b8739f). - Comprehensive refactoring of configuration system and bug fixes (0ad8221)
This is in addition to updates and bug fixes in the associated projects - ES6 Module Loader, SystemJS, SystemJS Builder, jspm-npm, jspm-github and jspm-registry-endpoint.