From 7c5a9595d3c98fdb181c8f0844973f4d58e858f0 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Tue, 14 Mar 2023 15:18:17 +0100 Subject: [PATCH] Create release (#62) Co-authored-by: github-actions[bot] --- .changeset/late-ducks-notice.md | 9 --------- .changeset/rude-dancers-grab.md | 7 ------- .changeset/seven-apples-nail.md | 7 ------- CHANGELOG.md | 20 ++++++++++++++++++++ package.json | 2 +- 5 files changed, 21 insertions(+), 24 deletions(-) delete mode 100644 .changeset/late-ducks-notice.md delete mode 100644 .changeset/rude-dancers-grab.md delete mode 100644 .changeset/seven-apples-nail.md diff --git a/.changeset/late-ducks-notice.md b/.changeset/late-ducks-notice.md deleted file mode 100644 index 4300ec3..0000000 --- a/.changeset/late-ducks-notice.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -'@fransvilhelm/wp-bundler': minor ---- - -Move away from multibundler setup - -Previously we initiated two separate esbuild process to build the modern and legacy outputs. This meant we had no way to output a good asset loader witouth waiting for both of the outputs to be done and merge them. - -With this approach the legacy output is moving into the main process again. Something that will speed up and make out lives much easier in the future. diff --git a/.changeset/rude-dancers-grab.md b/.changeset/rude-dancers-grab.md deleted file mode 100644 index 9a2fc1b..0000000 --- a/.changeset/rude-dancers-grab.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -'@fransvilhelm/wp-bundler': major ---- - -Make project esm only - -This project is now esm only. Generally it shouldn't affect you that much. But if you plan on building something on top of wp-bundler, using the exposed interfaces you need to be aware of this fact. diff --git a/.changeset/seven-apples-nail.md b/.changeset/seven-apples-nail.md deleted file mode 100644 index 7189c15..0000000 --- a/.changeset/seven-apples-nail.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -'@fransvilhelm/wp-bundler': major ---- - -Remove ability to call wp-bundler without sub commands - -Previously we allowed calling `wp-bundler` without `dev` or `build` sub commands, like it was from v1. This release removes that ability. From now on you must call `wp-bundler dev` or `wp-bundler build`. diff --git a/CHANGELOG.md b/CHANGELOG.md index 7da03a9..6c8f47a 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,25 @@ # @fransvilhelm/wp-bundler +## 4.0.0 + +### Major Changes + +- Make project esm only (by [@adambrgmn](https://github.com/adambrgmn) in [#66](https://github.com/adambrgmn/wp-bundler/pull/66)) + + This project is now esm only. Generally it shouldn't affect you that much. But if you plan on building something on top of wp-bundler, using the exposed interfaces you need to be aware of this fact. + +- Remove ability to call wp-bundler without sub commands (by [@adambrgmn](https://github.com/adambrgmn) in [#69](https://github.com/adambrgmn/wp-bundler/pull/69)) + + Previously we allowed calling `wp-bundler` without `dev` or `build` sub commands, like it was from v1. This release removes that ability. From now on you must call `wp-bundler dev` or `wp-bundler build`. + +### Minor Changes + +- Move away from multibundler setup (by [@adambrgmn](https://github.com/adambrgmn) in [#69](https://github.com/adambrgmn/wp-bundler/pull/69)) + + Previously we initiated two separate esbuild process to build the modern and legacy outputs. This meant we had no way to output a good asset loader witouth waiting for both of the outputs to be done and merge them. + + With this approach the legacy output is moving into the main process again. Something that will speed up and make out lives much easier in the future. + ## 3.0.1 ### Patch Changes diff --git a/package.json b/package.json index ecffe5d..ce69ed6 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "@fransvilhelm/wp-bundler", - "version": "3.0.1", + "version": "4.0.0", "description": "A fast bundler tailored for WordPress based on esbuild", "type": "module", "exports": {