Skip to content

Commit 6d1e242

Browse files
committed
Merge pull request #110 from morenoh149/patch-1
Add details on how to provide a github version
2 parents 9744d8b + f5d26b3 commit 6d1e242

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

README.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ Then start your app with `meteor` and follow the instructions.
2323
2424
## Defining Packages
2525
26-
Once the npm support has been initialized, you'll be having a file name called `packages.json` inside your app. Define packages on that file as shown below.
26+
Once npm support has been initialized, you'll have a file name called `packages.json` inside your app. Define packages in that file as shown below.
2727
2828
~~~json
2929
{
@@ -32,7 +32,7 @@ Once the npm support has been initialized, you'll be having a file name called `
3232
}
3333
~~~
3434
35-
> You must need to define absolute version number of the npm module
35+
> You must define an absolute version number for the npm module
3636
3737
If you need to install an npm module from a specific commit, use the syntax:
3838

@@ -41,6 +41,7 @@ If you need to install an npm module from a specific commit, use the syntax:
4141
"googleapis": "https://github.com/bradvogel/google-api-nodejs-client/archive/d945dabf416d58177b0c14da64e0d6038f0cc47b.tar.gz"
4242
}
4343
~~~
44+
The above can be generated using [github releases](https://github.com/blog/1547-release-your-software). You're going to want to use `<commit hash>.tar.gz` version, not `archive/<version number>.tar.gz`.
4445

4546
## Using Packages
4647

0 commit comments

Comments
 (0)