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.

Sign up for GitHub

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

Jump to bottom

Moving over to a single top level package evergreen or evergreen-ui #117

Closed
jeroenransijn opened this issue Jan 26, 2018 · 1 comment
Closed

Moving over to a single top level package evergreen or evergreen-ui #117

jeroenransijn opened this issue Jan 26, 2018 · 1 comment
Labels
high-priority improvement in-progress

Comments

@jeroenransijn
Copy link
Contributor

Read the complete background on this issue here: #103.

After having tried a Lerna mono-repo, we found that the benefits don't outweigh the downsides. The main issues are:

  • A lot of boilerplate to import components
  • Keeping dependencies in sync is a pain for the consumer
  • Publishing packages gets confusing
  • Harder to setup code splitting

That's why we are in the progress of moving towards a single evergreen-ui package.

I have made PoC codemod to move over current projects that use Evergreen. Which mainly internal projects at Segment.

  • We'll rename the current package folders from evergeen-colors into colors.
  • Test and run a codemod script on the current projects using Evergreen
@jeroenransijn jeroenransijn mentioned this issue Jan 26, 2018
Closed
@jeroenransijn
Copy link
Contributor Author

#125

@Rowno Rowno mentioned this issue Feb 6, 2018
Merged
9 tasks
@Rowno Rowno closed this as completed in #125 Feb 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
high-priority improvement in-progress
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jeroenransijn