-
Notifications
You must be signed in to change notification settings - Fork 3
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
Simplify the build pipeline #1385
Merged
Merged
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
🦋 Changeset detectedLatest commit: 9275d89 The changes in this PR will be included in the next version bump. This PR includes changesets to release 19 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
github-actions
bot
added
🛠 workspace
📦 npm
Affects a @guardian package on NPM
@guardian/libs
@guardian/browserslist-config
@guardian/eslint-config-typescript
@guardian/eslint-config
@guardian/prettier
@guardian/tsconfig
@guardian/ab-core
@guardian/ab-react
labels
Apr 26, 2024
sndrs
changed the title
make all packages modules, and build with
make all packages ES modules, and build with Apr 26, 2024
pkgroll
to local distpkgroll
to local dist
sndrs
commented
Apr 26, 2024
sndrs
commented
Apr 29, 2024
sndrs
commented
Apr 29, 2024
sndrs
added
the
🐥 Canaries
Triggers canary releases of any packages with changesets waiting.
label
Apr 29, 2024
sndrs
changed the title
make all packages ES modules, and build with
Simplify the build pipeline
May 7, 2024
pkgroll
to local dist
This was
linked to
issues
May 7, 2024
sndrs
added
the
🐥 Canaries
Triggers canary releases of any packages with changesets waiting.
label
May 7, 2024
sndrs
removed
the
🐥 Canaries
Triggers canary releases of any packages with changesets waiting.
label
May 7, 2024
oliverabrahams
approved these changes
May 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
@guardian/ab-core
@guardian/ab-react
@guardian/browserslist-config
@guardian/eslint-config
@guardian/eslint-config-typescript
@guardian/libs
@guardian/prettier
@guardian/tsconfig
📦 npm
Affects a @guardian package on NPM
run_chromatic
Runs chromatic when label is applied
🛠 workspace
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.
What are you changing?
updates the build/packages setup:
rollup
directly@csnx/npm-package
rollup-plugin-esbuild
androllup-plugin-dts
in place ofrollup-plugin-ts
dist
dirs and removes thepaths
config fromtsconfig
build
andvalidate-dist
tasks from packages that don't actually build anything (were just being copied to Nx's rootdist
dir)Why?
All packages that depend on sibling packages in the repo now consume their real
dist
files, not.ts
source files.it also surfaces the rollup config and package.json for each package more clearly.
our previous typescript plugin created some weird type issues (we think it was the plugin).
rollup-plugin-dts
is more commonly used hopefully more robust!Why is it so big?
we'd accumulated some tech debt that made each of these steps difficult to do alone - this was pairing/mobbing effort the whole team was involved in, so in effect it was reviewed in real time.
Co-authored-by: @oliverabrahams
Co-authored-by: @jamesmockett