-
Notifications
You must be signed in to change notification settings - Fork 55
removing yarn in favour of npm #464
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
Conversation
|
Variables changedNo variables changed |
3f16d01 to
cdbe49f
Compare
🟢 No design token changes found |
cdbe49f to
76cb846
Compare
951a933 to
37e38b5
Compare
|
Hey @rezrah it seems one big issue is that |
40c1ddf to
e8fe520
Compare
colebemis
left a comment
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.
✨
252c75b to
a41219e
Compare
11f5d96 to
07aa79e
Compare
07aa79e to
be1688a
Compare
be1688a to
2436050
Compare
2436050 to
c47f349
Compare
4ffcded to
58c1336
Compare
* removing yarn in favour of npm * remove yarn lock for storybook * rebuild lock files & remove unused failing import * trying webpack fix --------- Co-authored-by: Reza Rahman <[email protected]>
Summary
This fixes #425 by removing
yarnin favor ofnpmTodo
npm cinpx changesetas we do in some of the actions in any case? (@rezrah)List of notable changes:
yarn.lockpackage-lock.jsonnpm runandnpm ciWhat should reviewers focus on?
Contributor checklist:
Reviewer checklist: