-
Notifications
You must be signed in to change notification settings - Fork 505
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
Fix installation instructions #1012
Conversation
docs/source/contribute.rst
Outdated
conda activate voila | ||
|
||
# download voila from your GitHub fork | ||
git clone https://github.com/<your-github-username>/voila.git | ||
|
||
# install JS dependencies and build js assets | ||
cd voila/js | ||
cd voila | ||
npm install |
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.
Should it be yarn install
?
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 don't know, npm install
worked for me 😄
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.
But I see we have yarn.lock
files around so it seems we actually use yarn and not npm?
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.
No idea.
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 we shouldn't mix yarn and npm, so we need to make a choice. I guess if we have yarn around we should stop using npm. Or we remove the yarn.lock
and commit the package-lock.json
npm generates.
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 personally prefer npm
over yarn
but since we had the yarn.lock
already, we should stick with yarn
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.
+1 on sticking with yarn from my side. It seems to be faster and the lock file is smaller.
npm install -g yarn
yarn
can be installed from conda-forge.
Failed tests are not related. |
Thank @davidbrochart! |
@meeseeksdev please backport to 0.2.x |
…2-on-0.2.x Backport PR #1012 on branch 0.2.x (Fix installation instructions)
No description provided.