-
-
Notifications
You must be signed in to change notification settings - Fork 350
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
Change yarn to npm in TravisCI config #158
Conversation
Why? |
@ddavidebor Do you have gitter? I sent a message explaining my reasoning. I'll copy it below. Hello, I am the intern working on Jupyterlab and I’m currently encountering some issues around Travis and the use of yarn. Specifically, any use of
I looked it up and apparently yarn does some funny business related to copying the node_modules, see yarnpkg/yarn#1334 and DefinitelyTyped/DefinitelyTyped#18484 My conclusion was I should switch TravisCI to use npm only, instead of yarn. I wanted to get your thoughts on this, and any advice you may have concerning. |
I was working on a fix for a different branch (#157) and I kept getting failures. I tried to reproduce the changes on my machine using I apologize for all the grammar and spelling mistakes. |
@ddavidebor Sadly, If you have any advice, please let me know. If not I'll probably close and delete this branch. |
@ddavidebor Would it be possible to chat on gitter or some other platform about this? |
Yes but I do not think I am the most competent person in the matter here.
I mostly followed CI and app building, I have a limited understanding of
jupyterlab peculiarities regarding all the node modules behind the app.
Il gio 12 apr 2018, 18:46 Declan Kelly <notifications@github.com> ha
scritto:
… @ddavidebor <https://github.com/ddavidebor> Would it be possible to chat
on gitter or some other platform about this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#158 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AIot_g1uFFnXqkVTngH80HyAvVwnWF9tks5tn4THgaJpZM4TFtz1>
.
|
This adjustment of the sub-node_modules folder is not viable in the long-term. Package dependency versions will change and break this configuration.
Closing in favour of PR #162 |
No description provided.