Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More →
jspm - npm Package Compare versions
Comparing version 0.7.0-beta.20 to 0.7.0
| { | ||
| "name": "jspm", | ||
| "description": "", | ||
| "version": "0.7.0-beta.20", | ||
| "version": "0.7.0", | ||
| "main": "./api.js", | ||
@@ -6,0 +6,0 @@ "author": "", |
@@ -10,3 +10,2 @@ jspm CLI | ||
| * Creates the [SystemJS](https://github.com/systemjs/systemjs) version configuration file for the package. | ||
| * Supports [working with ES6 modules](#compiling-application-code). | ||
@@ -85,6 +84,6 @@ [Build into a bundle](#1-creating--bundle) or [inject a flat dependency tree for flat multiplexing](#2-creating--dependency-cache) in production. | ||
| No package.json found, would you like to create one? [yes]: | ||
| Would you like jspm to prefix its package.json properties under jspm? [yes]: | ||
| Enter packages folder [jspm_packages]: | ||
| Enter config file path [config.js]: | ||
| Configuration file config.js not found, create it? [y]: | ||
| ok Loader files downloaded successfully | ||
| ok Verified package.json at package.json | ||
@@ -94,6 +93,2 @@ Verified config file at config.js | ||
| The application name is used to require anything from the application code folder `lib`, instead of from the jspm registry. | ||
| A require to `app/main` will load `lib/main.js` in this example. | ||
| Sets up the package.json and configuration file. | ||
@@ -107,5 +102,10 @@ | ||
| Downloading loader files to jspm_packages | ||
| system@0.4.js | ||
| es6-module-loader@0.4.1.js | ||
| traceur@0.0.10.js | ||
| Looking up github:ModuleLoader/es6-module-loader | ||
| Looking up github:systemjs/systemjs | ||
| Looking up github:jmcriffey/bower-traceur | ||
| es6-module-loader@0.8.js | ||
| system@0.8.js | ||
| traceur-runtime@0.0.58.js | ||
| traceur@0.0.58.js | ||
| ok Loader files downloaded successfully | ||
| ``` | ||
@@ -220,6 +220,50 @@ | ||
| Use `-h` or `--https` to download with https instead of alternative protocols. | ||
| Use `-o` or `--override` to force-set the package override for a package that needs extra configuration. See https://github.com/jspm/registry#testing-package-overrides. | ||
| ## Development Workflows | ||
| ### Linking | ||
| Local linking allows linking local folders to be installed instead of using the remote versions of packages. | ||
| Linked packages still need to be linked into a full endpoint, package and version. | ||
| ``` | ||
| cd my-local-package | ||
| jspm link npm:pkg@1.2.3 | ||
| ok Package linked. | ||
| cd ../my-jspm-app | ||
| jspm install --link npm:pkg@1.2.3 | ||
| ``` | ||
| `my-jspm-app` gets a symlink to a globally linked version of `my-local-package`. But changes to `my-local-package` do require | ||
| running `jspm link npm:pkg@1.2.3` again to update the link cache, as jspm runs build operations on the package when adding npm compatibility. | ||
| ### Creating Custom Endpoints | ||
| You may wish to create your own custom endpoints, such as a private `npm` repo. | ||
| This can be done with: | ||
| ``` | ||
| jspm endpoint create myendpoint jspm-npm | ||
| npm registry to use [https://registry.npmjs.org]: | ||
| Would you like to configure authentication? [no]: y | ||
| Enter your npm username: mynpmusername | ||
| Enter your npm password: | ||
| ``` | ||
| We now have an `npm` endpoint based on a custom registry and authentication which can be used as expected: | ||
| ``` | ||
| jspm install myendpoint:package | ||
| ``` | ||
| You can also configure these same options for the existing `npm` endpoint if using a local npm mirror: | ||
| ``` | ||
| jspm endpoint config npm | ||
| ``` | ||
| ## Production Workflows | ||
@@ -257,3 +301,3 @@ | ||
| ### 2. Creating a Bundle excluding a dependency | ||
| #### Creating a Bundle excluding a dependency | ||
@@ -266,3 +310,3 @@ ``` | ||
| ### 3. Creating a Bundle adding another dependency | ||
| #### Creating a Bundle adding another dependency | ||
@@ -275,3 +319,3 @@ ``` | ||
| ### 4. Creating a Bundle both adding a dependency and excluding a dependency | ||
| #### Creating a Bundle both adding a dependency and excluding a dependency | ||
@@ -284,2 +328,14 @@ ``` | ||
| #### Loading a bundle automatically (inject) | ||
| If you don't want to include the bundle with a script tag, but rather load it only when it is needed, we can do: | ||
| ``` | ||
| jspm bundle app/main - app/core main-bundle.js --inject | ||
| ``` | ||
| The above will create the bundle, then inject configuration to tell the SystemJS loader what modules should be loaded from the `main-bundle.js` file. | ||
| As soon as one of these modules is requested, the bundle is loaded dynamically. | ||
| ### 5. Creating a Dependency Cache | ||
@@ -303,11 +359,2 @@ | ||
| ### Rate Limits | ||
| To set GitHub authentication to avoid rate limits, enter your GitHub credentials with: | ||
| ``` | ||
| jspm config github.username myusername | ||
| jspm config github.password mypassword | ||
| ``` | ||
| ### Further Reading | ||
@@ -314,0 +361,0 @@ |
New alerts
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Fixed alerts
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Improved metrics
- Total package byte prevSize
- increased by0.91%
160999
- Number of lines in readme file
- increased by15.02%
360
No dependency changes