-
Notifications
You must be signed in to change notification settings - Fork 333
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
Remove built govuk-frontend
from committed files
#3498
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
colinrotherham
force-pushed
the
review-app-user
branch
from
April 12, 2023 15:07
aff5e63
to
681bdbf
Compare
colinrotherham
force-pushed
the
delete-package-dist
branch
from
April 12, 2023 15:11
0ad6dd8
to
5171ce2
Compare
colinrotherham
force-pushed
the
review-app-user
branch
from
April 13, 2023 17:23
681bdbf
to
7e0828a
Compare
colinrotherham
force-pushed
the
delete-package-dist
branch
from
April 13, 2023 17:24
5171ce2
to
f59df26
Compare
colinrotherham
force-pushed
the
review-app-user
branch
from
April 13, 2023 17:46
7e0828a
to
45c7a52
Compare
colinrotherham
force-pushed
the
delete-package-dist
branch
from
April 13, 2023 17:48
f59df26
to
1be359c
Compare
colinrotherham
force-pushed
the
review-app-user
branch
2 times, most recently
from
April 18, 2023 15:14
08ec480
to
bfb6bab
Compare
colinrotherham
force-pushed
the
delete-package-dist
branch
from
April 18, 2023 15:14
1be359c
to
9f57050
Compare
govuk-design-system-ci
had a problem deploying
to
govuk-frontend-pr-3498
April 18, 2023 15:15
Failure
colinrotherham
force-pushed
the
delete-package-dist
branch
from
April 18, 2023 15:20
9f57050
to
99af93f
Compare
govuk-design-system-ci
had a problem deploying
to
govuk-frontend-pr-3498
April 18, 2023 15:20
Failure
colinrotherham
force-pushed
the
review-app-user
branch
from
April 19, 2023 19:51
bfb6bab
to
2d2d951
Compare
colinrotherham
force-pushed
the
delete-package-dist
branch
from
April 19, 2023 19:52
99af93f
to
bbc6d86
Compare
govuk-design-system-ci
had a problem deploying
to
govuk-frontend-pr-3498
April 19, 2023 19:53
Failure
colinrotherham
force-pushed
the
review-app-user
branch
from
April 20, 2023 08:08
2d2d951
to
abe7d7c
Compare
colinrotherham
force-pushed
the
delete-package-dist
branch
from
April 20, 2023 13:20
bbc6d86
to
427297e
Compare
colinrotherham
force-pushed
the
review-app-user
branch
2 times, most recently
from
April 21, 2023 16:00
08f1d4a
to
dd706d3
Compare
colinrotherham
force-pushed
the
delete-package-dist
branch
from
May 18, 2023 11:55
7ffa8cf
to
07786fe
Compare
But rebuild them during `predev`, `pretest` and `heroku-postbuild`
This breaking change moves the npm published `package/dist/package.json` to `package/package.json` Package exports will be updated in another commit
We currently ship with Node.js v4.2.0 support in `package.json` But ESLint is reporting that we need: * Node.js v14.0.0 for 'fs/promises' * Node.js v7.6.0 for Async functions Plus we’d need Node.js v12.19.0+ for wildcard package exports
Avoids breaking changes for Node.js (and bundlers that support package exports) Note: Sass load paths will still need the new `dist/` prefix
But excludes component data `*.yaml` which only exists in source
We can look at Node.js warnings on `npm install` in another PR but maintain ESLint Node.js compatibility checks using `settings.node.version`
We’re happy to make the `/dist` suffix a breaking change for v5
Our local packages don’t exist on https://registry.npmjs.org and can be skipped when outside npm workspaces
colinrotherham
force-pushed
the
delete-package-dist
branch
from
May 18, 2023 13:12
683c272
to
1a0b18a
Compare
romaricpascal
approved these changes
May 18, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Worked OK for dev
(including watch), build:package
as well as using npm link
or a pre-release branch to use it in the Prototype Kit 🎉
This was referenced May 19, 2023
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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 removes the
govuk-frontend
build output we use fornpm publish
This was known as the ./package directory until it moved to ./packages/govuk-frontend/dist in:
govuk-frontend
via local package #3491We don't need to commit it as we rebuild it during GitHub Actions tests
But it also addresses other concerns found during the performance work:
Our build outputs ESM files but we only test the UMD bundlesOur build outputs JSON component data, but we use ./src insteadPoint 1) has been resolved in #3491
Point 4) has been deemed acceptable for now
Once deleted, we can import from the built
govuk-frontend
instead