Skip to content

Releases: jspm/jspm-cli

jspm 0.11.0

30 Jan 13:03
Compare
Choose a tag to compare

Features

Bug Fixes

  • Fix app path in windows (72d9bee)
  • Link directories.lib fix (8553d98)

GitHub endpoint

npm endpoint

jspm 0.10.6

15 Jan 11:50
Compare
Choose a tag to compare

Bug fix for install --lock when there is no lock present (8ebd0f3).

jspm 0.10.5

15 Jan 09:55
Compare
Choose a tag to compare

Lots of bug fixes, thanks so everyone who reported these!

Bug Fixes

Features

  • Setting registry: jspm is no longer mandatory within overrides that have dependencies, and implied by default (2f50f18, 8d80d85, see #360).
  • Command shortcuts like jspm i for install etc (157eb51)
  • Experimental jspm resolve --only github:components/jquery@2.0.0 feature - ensures that the only version installed of a given package name is the version specified, regardless of version constraints.
  • API installs use default prompts instead of stalling (f91375b)

jspm 0.10.4

08 Jan 17:50
Compare
Choose a tag to compare

Features

  • jspm unbundle also removes depCache (b76f3ae)
  • Endpoint API 1.3 - allow endpoints to invalidate their own cache through custom versionString alterations (03625f5).

Bug Fixes

  • Linking postload bug introduced in 0.10 (e25e434)
  • Update module detection code to SystemJS latest and correctly handle System.register alias modules (451100c)

jspm GitHub 0.9.9

jspm npm 0.15.1

jspm 0.10.3

02 Jan 21:15
Compare
Choose a tag to compare

Correction to 0.10.2.

jspm 0.10.2

02 Jan 16:49
Compare
Choose a tag to compare

Patches install error #348

jspm 0.10.1

02 Jan 15:57
Compare
Choose a tag to compare

jspm CLI features

  • Endpoint API v2 post-install dependencies feature to allow Node core libs downloaded only when used (c5125f1)
  • Upgrade path to jspm-npm@0.15 (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 - eg jspm 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

jspm npm bug fixes

jspm 0.10.0

26 Dec 16:00
Compare
Choose a tag to compare

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 where app is the current project package name, and lib is the directories.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

  • Fix jspm install --unlink (5480413)
  • Lib folder linking fix (8eee3c7)
  • Fix bug on jspm install with no dependencies in package.json (7fb2e67)
  • Fixes em file errors by upgrading and using graceful-fs everywhere.

jspm 0.9.0

21 Nov 13:24
Compare
Choose a tag to compare

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 committing config.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 name underscore by default - this is to discourage code containing requires like require('npm:underscore') and ensure all requires are always portable.
  • jspm update will update all dependencies as defined in the package.json
  • jspm clean will remove orhpaned dependencies, and clear ununsed packages from jspm_packages.
  • jspm uninstall updated to apply jspm 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 and jspm 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 with import 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

18 Nov 15:27
Compare
Choose a tag to compare

Features

Bug Fixes

  • Fix windows paths support (ad475f8)
  • Fix global / local jspm install detection (074cb6b)
  • Fix jspm init defaults to work outside of the package.json folder (cd92fb1)
  • Semver fix (041abf0)
  • Ensure jspm bundling respects the baseURL (4f18299)
  • Ensure jspm link installs dependencies (7930cd8)