dev: use turbopack for local development #2685
Merged
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.
Summary
This PR sets up turbopack for local development for apps using the component library. This should result in much faster development rebuilds.
In order to do this, I had to ensure that the component library is getting built with tsc separately from the app code. This is because turbopack does not support extension aliases. This is probably fine as the extension aliases were always a bit of a hack, and I'd been meaning to do the component-library build separately for a long time anyways, as the prior approach would only work assuming that the tsconfig is identical which may not always be true. This issue also required updating all the
.jsimports to.jsxwhere appropriate in the component library.Turbopack also does not support the
:exportICSS directive so I also had to make some minor modifications in the few places we were using this.Rationale
This should significantly speed up local development.
How has this been tested?