Skip to content
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

Component hell & how to try and escape #62

Open
nk2580 opened this issue Feb 8, 2019 · 12 comments
Open

Component hell & how to try and escape #62

nk2580 opened this issue Feb 8, 2019 · 12 comments

Comments

@nk2580
Copy link

nk2580 commented Feb 8, 2019

Summary of talk

a journey through component sharing and the difficulties it creates

Details

Title of the Talk
Component hell & how to try and escape

Description of the Talk
a walkthrough of the experiences, key learning and wishlists for component sharing in React applications. the challenges faced integrating Bit, Lerna, Yarn workspaces and my eventual preferred solution (basically an NPM package with some strict tooling).

Length of the Talk
Approximately 8 Minutes

@loklaan
Copy link
Contributor

loklaan commented Feb 9, 2019

@nk2580 Thanks for making the issue, looking forward to this one 😻
Want to do it during the March meetup?

@nk2580
Copy link
Author

nk2580 commented Feb 10, 2019

@loklaan happy to talk at either the February or March events.

@loklaan
Copy link
Contributor

loklaan commented Feb 21, 2019

March is ideal! 😸 I'll add you to the next one.

Also I'd like to say thanks, it's lovely to get early speaker buy-in!

@nk2580
Copy link
Author

nk2580 commented Feb 21, 2019

@loklaan happy to do March, actually starting the Brisbane Flutter community on the 28th so timing ends up working better.

@loklaan
Copy link
Contributor

loklaan commented Feb 21, 2019

@nk2580 We're changing up the date actually! You're the first to know. Last week of the month was getting to heavy with other meetup's so we've jumped back to the third week (where we were most of last year).

@loklaan
Copy link
Contributor

loklaan commented Mar 10, 2019

Hey @nk2580, how're ya travelling for this talk?
Just a friendly reminder that the event is on next week, and that I'm stoked to hear you present! 😊

@nk2580
Copy link
Author

nk2580 commented Mar 27, 2019

so it would seem that the entire issue i was having can be really easily resolved with this facebook/create-react-app#1333 (comment)

my talk is now no longer valid, sorry guys

@nk2580 nk2580 closed this as completed Mar 27, 2019
@loklaan
Copy link
Contributor

loklaan commented Mar 27, 2019

@loklaan
Copy link
Contributor

loklaan commented Mar 27, 2019

That would be a great end a talk actually haha, but I don't think it invalidates anything.

Not to mention not everyone will/should use CRA.

How about a talk on using CRA in a monorepo?

@nk2580
Copy link
Author

nk2580 commented Mar 27, 2019

Fair Enough.... can do that instead.

@nk2580 nk2580 reopened this Mar 27, 2019
@basher
Copy link

basher commented Mar 27, 2019

so it would seem that the entire issue i was having can be really easily resolved with this facebook/create-react-app#1333 (comment)

my talk is now no longer valid, sorry guys

@nk2580
Nik, I'm glad you found my solution helpful. I can't begin to tell you how frustrating the whole process was!!

You might be interested to know that lerna add does not allow me to import/use different versions of the Storybook library (which I've published to a private NPM repo).

i.e. using commands like the following does not update library versions in each consumer app:

lerna add my-storybook-lib --scope=my-consumer-app1 --dev
lerna add [email protected] --scope=my-consumer-app2 --dev --exact

Instead, I'm now using lerna update wizard to manage versioned dependencies in my consumer apps.

@nk2580
Copy link
Author

nk2580 commented Mar 27, 2019

@basher thankfully my use case allows me to sync versions of create react app and storybook across all my packages.

This is a good example of a note that should be added to the docs though

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants