| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
rescript
npm i https://pkg.pr.new/rescript-lang/rescript@8230
npm i https://pkg.pr.new/rescript-lang/rescript/@rescript/darwin-arm64@8230
npm i https://pkg.pr.new/rescript-lang/rescript/@rescript/darwin-x64@8230
npm i https://pkg.pr.new/rescript-lang/rescript/@rescript/linux-arm64@8230
npm i https://pkg.pr.new/rescript-lang/rescript/@rescript/linux-x64@8230
npm i https://pkg.pr.new/rescript-lang/rescript/@rescript/runtime@8230
npm i https://pkg.pr.new/rescript-lang/rescript/@rescript/win32-x64@8230 commit: c3dfc0b |
Sorry, something went wrong.
| echo 'eval $(opam env)' >> ~/.bashrc | ||
|
|
||
| nvm install | ||
|
|
There was a problem hiding this comment.
Why are we removing this part?
Sorry, something went wrong.
There was a problem hiding this comment.
shell setup is now taken care of in opam init.
nvm install was not working because postCreate.sh gets run in a degraded shell env that can't find nvm so it was useless, nvm does run normally in a dev container terminal though and node version gets correctly set up.
Sorry, something went wrong.
There was a problem hiding this comment.
Ah I see --enable-shell-hook
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
it speeds up the test a bit but opam install has to be in postCreate.sh because there's no access to the repo in the docker build phase.