Skip to content
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

Update install guidelines #269

Merged
merged 1 commit into from
Aug 28, 2018
Merged

Conversation

kasicka
Copy link
Contributor

@kasicka kasicka commented Jun 21, 2018

No description provided.

```

If you still wish to use `yarn` instead of `nodejs-yarn`, the best way is to use bash alias.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you include the alias example, please?


```
$ sudo dnf install nodejs --releasever=25
$ nodejs-yarn add request
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd add a comment describing what is done, like so:

# Install package request using nodejs-yarn
[ . . ]
# Install package request using yarnpkg


```
$ sudo dnf install npm
$ dnf info nodejs
$ dnf info nodejs --enablerepo rawhide
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rawhide repository is not included in basic Fedora install AFAIK, so this wouldn't work.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will soon work with just --releasever=30 instead of --enablerepo rawhide, right?

@@ -4,36 +4,45 @@ subsection: nodejs
section: tech-languages
order: 1
version: LTS
Copy link
Contributor

@pvalena pvalena Jun 25, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

version variable is no longer used anywhere, could you remove it?

@pvalena
Copy link
Contributor

pvalena commented Aug 21, 2018

This branch is conflicting atm, please fix it.

@pvalena
Copy link
Contributor

pvalena commented Aug 28, 2018

In general this looks fine.
Thanks for the PR!

@pvalena pvalena merged commit e191f9a into developer-portal:master Aug 28, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants