-
Notifications
You must be signed in to change notification settings - Fork 14
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
Configure lerna to use jlpm
as npm client
#279
Conversation
yarn is bundled at the correct version with jlpm; installing it separately can cause trouble!
Preview using JupyterLite: appsharing.space |
Integration tests report: appsharing.space |
Docs preview: appsharing.space |
|
||
``jlpm run watch`` will sit and wait for a change once started. Edit a file | ||
to trigger a build. | ||
|
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.
This was true before this PR, but noticed it again during testing and figured it deserved a callout in the docs since it's a bit different behavior from most other "watch" tools I've used.
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.
Looks good, thanks @mfisher87
Should we also update the workflows for consistency ?
Are you referring to GitHub Actions workflows? I think yes, but that feels like a larger undertaking and less urgent. I'd like to prioritize that work separately from this PR if y'all agree! |
👍 let's postpone it. |
Resolves #253
Our contributing docs included instructions to install yarn at a specific version.
jlpm
comes bundled with the correct version of yarn, so we don't need that! This change simplifies environment setup.Check links is currently broken due to an upstream bug. See #278