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.jsnow 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.jswhen upgrading.jspm installwill now act as a reproducible install, like npm shrinkwrap, and will never alter the existing config resolutions.jspm install jquery --lockwill act as a stable install, not altering any existing config resolutions.jspm install npm:underscorewill install into the nameunderscoreby default - this is to discourage code containing requires likerequire('npm:underscore')and ensure all requires are always portable.jspm updatewill update all dependencies as defined in the package.jsonjspm cleanwill remove orhpaned dependencies, and clear ununsed packages fromjspm_packages.jspm uninstallupdated to applyjspm cleanby default.jspm inspectwill show a nice list of all packages and versions.jspm inspect --forkswill show the current forks.jspm inspect github:some/packagewill show the version resolution constraints for a given package.jspm linkandjspm install --linkhave been refined and optimized.jspm run moduleNamecan be used to execute on the server,jspm install nodelibssupports 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.