mirror of
https://github.com/systemjs/systemjs.git
synced 2026-01-25 14:57:38 +00:00
Update README.md
This commit is contained in:
parent
0c5c7ed0fb
commit
b5d0dbcfbc
@ -22,7 +22,7 @@ Getting Started
|
||||
4. [Loading External Packages from Endpoints](#loading-external-packages-from-endpoints)
|
||||
5. [Map Configuration](#map-configuration)
|
||||
6. [Loading External Packages from the jspm Registry](#loading-external-packages-from-the-jspm-registry)
|
||||
7. [Installing Libraries Locally](#installing-libraries-locally)
|
||||
7. [Installing Packages Locally](#installing-packages-locally)
|
||||
8. [Package Configuration](#package-configuration)
|
||||
9. [Cache Busting](#cache-busting)
|
||||
10. [Plugins](#plugins)
|
||||
@ -243,7 +243,7 @@ This is far better than specifying the full endpoint directly as it makes it ver
|
||||
|
||||
It can be difficult to know exactly what the most maintained endpoint is for a specific package and remember this endpoint each time.
|
||||
|
||||
Instead of needing to know `github:twbs/bootstrap` is the maintained package endpoint for Bootstrap, the jspm registry provides a simple service to remember the main endpoint for libraries.
|
||||
Instead of needing to know `github:twbs/bootstrap` is the maintained package endpoint for Bootstrap, the jspm registry provides a simple service to remember the main endpoint for a package.
|
||||
|
||||
We simply write:
|
||||
|
||||
@ -320,7 +320,7 @@ jspm.config({
|
||||
});
|
||||
```
|
||||
|
||||
### Installing Libraries Locally
|
||||
### Installing Packages Locally
|
||||
|
||||
While the CDN endpoints make it very convenient to create and load modules without the friction of installation, it is easy to switch to installing packages locally at any time.
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user