mowen233/jspm-registry
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

clarification

Browse Source
This commit is contained in:
Guy Bedford
2013-09-16 11:47:05 +02:00
parent bb5c9e87ee
commit 0dd3442d54
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+3 -3
View File
@@ -25,12 +25,12 @@ While the registry is small enough, all registry entries are managed through Git
It is simply a shorthand for specifying the main entry point when the package is requested directly by name. It is simply a shorthand for specifying the main entry point when the package is requested directly by name.
* Further customizations of package configurations for jspm should be provided in the package.json file * Further customizations of package configurations for jspm should be provided in the package.json file
for a package. If you do not have direct access to the source package, use a package override. for a package. If you do not have direct access to the source package, use a package.json override.
Package Overrides Package.json Overrides
--- ---
The registry provides a `package.json` override system for updating package configuration associated with jspm. The registry provides a package.json override system for updating package configuration associated with jspm.
The overrides are located in the `package-overrides` folder of this repo, with the folder format: The overrides are located in the `package-overrides` folder of this repo, with the folder format: