-
Notifications
You must be signed in to change notification settings - Fork 404
Monorepo Updates: Yarn, Lerna Fixed, Node v12, etc #1071
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
…when bootstrapping OR when publishing to NPM
@sghoweri this is incredible! Thank you so much for taking on so much. Will review in earnest this weekend. Onward! |
@@ -1 +1 @@ | |||
10.0.0 | |||
12.9.0 |
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.
a small nit for next time - so we're on the same page - i like to adhere to the guidance that production apps should use ACTIVE
, not CURRENT
according to this schedule. In this case, we are talking a few days, but it's wanted to bring attention to it.
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.
Totally fair — happy to bump to down to 11.x (but yep, 9 days to go till LTS!).
LMK if you think we should change this before merging down.
No it's totally fine, a couple days doesn't matter. And odd numbers are
usually for developing new node features so I tend to stay away too.
…On Sat, Oct 12, 2019, 4:10 PM Salem Ghoweri ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In .nvmrc
<#1071 (comment)>
:
> @@ -1 +1 @@
-10.0.0
+12.9.0
Totally fair — happy to bump to down to 11.x (but yep, 9 days to go till
LTS!).
LMK if you think we should change this before merging down.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
<#1071?email_source=notifications&email_token=AACI3Q7K3DUURR2DBPED7V3QOI4K7A5CNFSM4JADAIL2YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCHYT35A#discussion_r334253534>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACI3Q7ICXKWXFR4VORQ65LQOI4K7ANCNFSM4JADAILQ>
.
|
very excited for this - but i might not get to it til next week - vacation soon |
@sghoweri !!!! |
I took a survey of existing monorepo packages, to better understand if we should change our
as table
judging from this - i think we need to move everything up to 4.1.1 ? https://github.com/pattern-lab/starterkit-handlebars-vanilla should really move into the monorepo, with this linked repo and anything else still hanging around independently either archived or outright deleted |
@sghoweri curious if you have time to read the above and concur before next release |
@bmuenzenmeyer taking a look!! |
@bmuenzenmeyer see answers below:
👍 I'd love to see us keep working on the React engine (and perhaps that work opens the door to other JS-driven options) but yeah, it needs more work. Perhaps update the React engine package.json to be marked as private (temporarily) until we're ready to push out further updates?
Yes please!! For example, Browser Sync could be an excellent off the shelf replacement!
I'm inclined to say
Yes please! |
yeah i am fine with either - i just didnt know if manually setting it to 5 would increment it to 6 upon release. i suppose there is one way to find out. lerna has dry run capability, IIRC
we used to use that but i was convinced to move away from it by a former contributor. anything that makes our life easier, meets the needs of users, and is secure, I am for
that's a good idea |
…-updates Monorepo Updates: Yarn, Lerna Fixed, Node v12, etc
Summary
Closes #1040