Skip to content

Commit 64418d0

Browse files
authored
Update README.md
1 parent ffdec53 commit 64418d0

1 file changed

Lines changed: 14 additions & 1 deletion

File tree

README.md

Lines changed: 14 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,13 @@ We will come up with a long term solution at some point.
5959

6060

6161
## Making It Your Project
62-
`ExampleProject` is meant to be the starting point of your own project.
62+
`ExampleProject` is meant to be the starting point of your own project. You'll want
63+
to make use of existing libraries in your app, so
64+
browse the growing set of `opam` packages ported to `npm` under
65+
[`opam-alpha`](https://www.npmjs.com/~opam-alpha#packages). If there's something
66+
that hasn't yet been ported from `opam`, make a pull request to
67+
[this repo](https://github.com/yunxing/opam-npm/) and the package will automatically
68+
be ported (as soon as the daemon picks it up).
6369

6470
##### Add Another Dependency
6571

@@ -77,6 +83,13 @@ rebuilt as a result of the `install` was not designed to build in an idempotent
7783
In that case, just add the new dependency to your `package.json` `"dependencies"`,
7884
`rm -r node_modules`, and then run `npm install`. This installs from a clean slate.
7985

86+
87+
> Note: `opam-alpha` is "alpha" - we may move to a new namespace `opam-beta`
88+
once we apply the lessons we've learned from `opam-alpha`. All the should exist
89+
as they are, but a next generation `opam-beta` universe on `npm` would have
90+
everything `opam-alpha` has (and then some). The work to upgrade your projects
91+
will likely be minimal.
92+
8093
### What's happening
8194
- `npm install` will download and install all your dependencies, and run the
8295
`postinstall` steps for all of those dependencies, and then finally the

0 commit comments

Comments
 (0)