@dotcom-tool-kit/webpack 4.4.1 → 5.0.1-beta.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/package.json +7 -7
  2. package/readme.md +2 -2
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@dotcom-tool-kit/webpack",
3
- "version": "4.4.1",
3
+ "version": "5.0.1-beta.1",
4
4
  "main": "lib",
5
5
  "description": "",
6
6
  "author": "FT.com Platforms Team <platforms-team.customer-products@ft.com>",
@@ -17,15 +17,15 @@
17
17
  "test": "cd ../../ ; npx jest --silent --projects plugins/webpack"
18
18
  },
19
19
  "dependencies": {
20
- "@dotcom-tool-kit/base": "^1.3.1",
21
- "@dotcom-tool-kit/error": "^4.1.1",
22
- "@dotcom-tool-kit/logger": "^4.2.2",
20
+ "@dotcom-tool-kit/base": "^4.0.0-beta.1",
21
+ "@dotcom-tool-kit/error": "^5.0.0",
22
+ "@dotcom-tool-kit/logger": "^5.0.0",
23
23
  "tslib": "^2.8.1",
24
24
  "webpack-cli": "^4.6.0",
25
25
  "zod": "^3.24.4"
26
26
  },
27
27
  "peerDependencies": {
28
- "dotcom-tool-kit": "4.x",
28
+ "dotcom-tool-kit": "^5.0.1-beta.1",
29
29
  "webpack": "4.x.x || 5.x.x"
30
30
  },
31
31
  "devDependencies": {
@@ -41,6 +41,6 @@
41
41
  "extends": "../../package.json"
42
42
  },
43
43
  "engines": {
44
- "node": "18.x || 20.x || 22.x"
44
+ "node": ">=20.x"
45
45
  }
46
- }
46
+ }
package/readme.md CHANGED
@@ -19,11 +19,11 @@ plugins:
19
19
 
20
20
  ### Building with Webpack locally
21
21
 
22
- For local development, by default the `WebpackDevelopment` task runs on the `build:local` command, and `WebpackWatch` runs on `run:local`. One plugin that provides these commands is [`npm`](../npm), allowing you to run Webpack with `npm run build` and `npm start`. `WebpackWatch` runs Webpack in the background, allowing it to run alongside your other tasks that run on `run:local`, which lets you run e.g. your app with the [`node`](../node) plugin in parallel with Webpack.
22
+ For local development, by default the `Webpack` task runs in `development` mode on the `build:local` command, and runs in `watch` mode on `run:local`. One plugin that provides these commands is [`npm`](../npm), allowing you to run Webpack with `npm run build` and `npm start`.
23
23
 
24
24
  ### Building with Webpack on CI and remote apps
25
25
 
26
- The `WebpackProduction` task runs on the `build:ci` and `build:remote` commands by default. `build:ci` is for compiling an app's source in CI jobs, and is provided by plugins like [`circleci`](../circleci/). `build:remote` compiles an app for running on a production or testing server, and can be provided by plugins like [`heroku`](../heroku/).
26
+ The `Webpack` task runs in `production` mode on the `build:ci` command by default. `build:ci` is for compiling an app's source in CI jobs, and is provided by plugins like [`circleci`](../circleci/).
27
27
 
28
28
  ### Running on another command
29
29
  You can also configure Webpack to run on any other command; for example, if you want to run it with `npm run test` via the `npm` plugin, you can manually configure Webpack to run on `npm`'s `test:local` command: