New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using specific Node version #262
Conversation
INSTALL.md
Outdated
|
||
```bash | ||
nvm install 10.13.0 | ||
nvm use 10.13.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a difference between Node 10.x versions?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
well, minor TBH, we try to stick with latest LTS
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so, brew install node@10
should be good too no?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I could add as a macos alternative
BTW, any reason why not to just use npm instead of yarn? I don't see clear path how yarn gets productized, so just going back to npm does not sound as that big a deal. |
@mikz My idea was after #57 is merged, ditch yarn and use just npm. But @hallelujah mentioned the alternative of somehow productize yarn/ocaml since it's default for Rails 5. Still we haven't explored much the latest alternative. |
@didierofrivia I don't see yarn productization as something feasible or our task in the first place. Yarn is just a package manager. It is irrelevant for rails what package manager we use to install dependencies. We only need to change relevant rake tasks to run npm instead. |
@mikz I wholeheartedly agree with you 👍 |
Please do not forget about https://github.com/3scale/porta/blob/master/openshift/system/contrib/scl_enable#L4 And build an image to try this out before CR1 if you want to have it in CR1 (optional IMO) |
06c3afc
Codecov Report
@@ Coverage Diff @@
## master #262 +/- ##
==========================================
+ Coverage 92.58% 92.58% +<.01%
==========================================
Files 2359 2359
Lines 75471 75471
==========================================
+ Hits 69874 69875 +1
+ Misses 5597 5596 -1
Continue to review full report at Codecov.
|
0915404
to
8691069
Compare
UPDATE: Latest stable RHEL Node version is 8.3.0, so updating this PR |
cef0f0b
to
a5ab79b
Compare
INSTALL.md
Outdated
|
||
The project supports **Version: 8.X.X**. | ||
|
||
You might want to use [nvm](https://github.com/creationix/nvm/) to install and work with a specific Node versions: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Typo, it should be specific Node version
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I wanted with specific node versions
without the a
hehe, thanks!
What this PR does / why we need it:
Since we still can't productise Yarn, we need to commit our webpack packs and having different Node version resolves to different packs committed.
Which issue(s) this PR fixes
This will avoid having different packs every time webpack builds them. It also fixed a webpacker - node-sass issue.
Verification steps
rm -rf node_modules
npm install
rake webpack:production