-
Notifications
You must be signed in to change notification settings - Fork 339
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
Investigate using the packages
folder convention
#3490
Closed
Closed
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
53aca35
to
e5f9f99
Compare
1c4beb8
to
07ddf40
Compare
e5f9f99
to
90fdd81
Compare
07ddf40
to
2901d78
Compare
90fdd81
to
fbedabd
Compare
2901d78
to
42cbfea
Compare
d98a34e
to
84248f7
Compare
42cbfea
to
3bf8936
Compare
84248f7
to
9e73e25
Compare
3bf8936
to
cfe5a88
Compare
9e73e25
to
9e4cf79
Compare
cfe5a88
to
30344aa
Compare
9e4cf79
to
5f9b2d2
Compare
In preparation for build artifacts being deleted, package will need utility tasks to run (on watch) during development
But rebuild them during `predev`, `pretest` and `heroku-postbuild`
Ignores the ‘unlink’ (delete) event otherwise Review app watch tasks trigger when `govuk-frontend` “clean” runs. Built code is not available at this point
This breaking change moves the wrapper `package/dist/package.json` to `package/package.json` Package exports will be updated in another commit
Avoids breaking changes for Node.js (and bundlers that support package exports) Note: Sass load paths will still need the new `dist/` prefix
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
028a31c
to
3523aef
Compare
83241a7
to
10dda9f
Compare
packages
folder convention
Moves `govuk-frontend` and the Review app packages into “packages” https://docs.npmjs.com/cli/v9/using-npm/workspaces#defining-workspaces
The switch to `packages/*` has caused the review app to build _before_ `govuk-frontend` which threw errors on missing Sass and JavaScript
10dda9f
to
fe4eac8
Compare
7a3eb35
to
a9abcf1
Compare
It's a keeper. I've folded this work into: |
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.
Moves
govuk-frontend
and the Review app packages into “packages”This follows the
npm workspaces
default which we see in other tools:dequelabs/axe-core-npm/packages
babel/babel/packages
cssnano/cssnano/packages
eslint/eslint/packages
facebook/jest/packages
webdriverio/webdriverio/packages
But keeping
shared
at project rootAfter