chore: monorepo package structure #5944
Open
+2,081
−632
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
briangregoryholmes
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR proposes migrating our shared code structure to follow a more traditional monorepo organization.
Namely, there is a new top level
packagesfolder that houses isolated modules of shared/reusable code. Each of these will have their own dependencies, scripts, versions, test suites and will import from each other as you would import from any other package. This PR begins this process by creating three packages:utils,eventsandactions.This is an open discussion, but I anticipate creating the following additional packages based on our existing code:
ui,state,formatting,query,icons,time,features,metricsand other packages for shared configuration.