Version Packages (#16)

This PR was opened by the [Changesets
release](https://github.com/changesets/action) GitHub action. When
you're ready to do a release, you can merge this and the packages will
be published to npm automatically. If you're not ready to do a release
yet, that's fine, whenever you add more changesets to main, this PR will
be updated.


# Releases
## @hwy-js/build@0.4.0

### Minor Changes

- 772708e: First off, huge shoutout to @jharrell for his debugging and
research assistance on this PR related to adding Cloudflare Pages
support! Thank you!

    Cloudflare Pages is now supported! Closes issue #6.

    Added changesets. Closes issue #14.

Adds a hwy.config.ts / hwy.config.js file to the root of your project
for setting up dev settings and deployment target, and probably other
things in the future. As annoying as config files are, this simplifies a
lot of things and is not too much to ask for a framework.

Removes a lot of complexity / variance in build commands and deploy
target hacks, as now we can just read the deployment target from the Hwy
config and handle everything in Hwy's centralized build step.

Adds a new @hwy-js/build package, splitting up the live refresh stuff
(stays in @hwy-js/dev) from the build stuff.

    In your src/main.tsx file:

{hwyDev?.DevLiveRefreshScript()} is now just <DevLiveRefreshScript />
<ClientEntryScript /> is now <ClientScripts
activePathData={activePathData} />. This is to enable the new client
scripts functionality mentioned below.
Added an option to ship client-side JS (including from TS files if you
want) by adding a sibling page-name.client.ts or page-name.client.js
file to your page. This becomes basically global JS for that page, and
anything imported will be bundled into that page's script, which is
built into the public folder and referenced in the document head when
you visit that page. This will be better documented later. Closes issue
#15.

### Patch Changes

-   772708e: rmv rmSync instance, not really necessary
-   772708e: init changesets
-   772708e: tweak build step, auto read latest version in create-hwy

## hwy@0.4.0

### Minor Changes

- 772708e: First off, huge shoutout to @jharrell for his debugging and
research assistance on this PR related to adding Cloudflare Pages
support! Thank you!

    Cloudflare Pages is now supported! Closes issue #6.

    Added changesets. Closes issue #14.

Adds a hwy.config.ts / hwy.config.js file to the root of your project
for setting up dev settings and deployment target, and probably other
things in the future. As annoying as config files are, this simplifies a
lot of things and is not too much to ask for a framework.

Removes a lot of complexity / variance in build commands and deploy
target hacks, as now we can just read the deployment target from the Hwy
config and handle everything in Hwy's centralized build step.

Adds a new @hwy-js/build package, splitting up the live refresh stuff
(stays in @hwy-js/dev) from the build stuff.

    In your src/main.tsx file:

{hwyDev?.DevLiveRefreshScript()} is now just <DevLiveRefreshScript />
<ClientEntryScript /> is now <ClientScripts
activePathData={activePathData} />. This is to enable the new client
scripts functionality mentioned below.
Added an option to ship client-side JS (including from TS files if you
want) by adding a sibling page-name.client.ts or page-name.client.js
file to your page. This becomes basically global JS for that page, and
anything imported will be bundled into that page's script, which is
built into the public folder and referenced in the document head when
you visit that page. This will be better documented later. Closes issue
#15.

### Patch Changes

-   772708e: rm console log
-   772708e: init changesets

## create-hwy@0.4.0

### Minor Changes

- 772708e: First off, huge shoutout to @jharrell for his debugging and
research assistance on this PR related to adding Cloudflare Pages
support! Thank you!

    Cloudflare Pages is now supported! Closes issue #6.

    Added changesets. Closes issue #14.

Adds a hwy.config.ts / hwy.config.js file to the root of your project
for setting up dev settings and deployment target, and probably other
things in the future. As annoying as config files are, this simplifies a
lot of things and is not too much to ask for a framework.

Removes a lot of complexity / variance in build commands and deploy
target hacks, as now we can just read the deployment target from the Hwy
config and handle everything in Hwy's centralized build step.

Adds a new @hwy-js/build package, splitting up the live refresh stuff
(stays in @hwy-js/dev) from the build stuff.

    In your src/main.tsx file:

{hwyDev?.DevLiveRefreshScript()} is now just <DevLiveRefreshScript />
<ClientEntryScript /> is now <ClientScripts
activePathData={activePathData} />. This is to enable the new client
scripts functionality mentioned below.
Added an option to ship client-side JS (including from TS files if you
want) by adding a sibling page-name.client.ts or page-name.client.js
file to your page. This becomes basically global JS for that page, and
anything imported will be bundled into that page's script, which is
built into the public folder and referenced in the document head when
you visit that page. This will be better documented later. Closes issue
#15.

### Patch Changes

-   772708e: update ClientEntryScript to ClientScripts
-   772708e: init changesets
-   772708e: tweak build step, auto read latest version in create-hwy

## @hwy-js/dev@0.4.0

### Minor Changes

- 772708e: First off, huge shoutout to @jharrell for his debugging and
research assistance on this PR related to adding Cloudflare Pages
support! Thank you!

    Cloudflare Pages is now supported! Closes issue #6.

    Added changesets. Closes issue #14.

Adds a hwy.config.ts / hwy.config.js file to the root of your project
for setting up dev settings and deployment target, and probably other
things in the future. As annoying as config files are, this simplifies a
lot of things and is not too much to ask for a framework.

Removes a lot of complexity / variance in build commands and deploy
target hacks, as now we can just read the deployment target from the Hwy
config and handle everything in Hwy's centralized build step.

Adds a new @hwy-js/build package, splitting up the live refresh stuff
(stays in @hwy-js/dev) from the build stuff.

    In your src/main.tsx file:

{hwyDev?.DevLiveRefreshScript()} is now just <DevLiveRefreshScript />
<ClientEntryScript /> is now <ClientScripts
activePathData={activePathData} />. This is to enable the new client
scripts functionality mentioned below.
Added an option to ship client-side JS (including from TS files if you
want) by adding a sibling page-name.client.ts or page-name.client.js
file to your page. This becomes basically global JS for that page, and
anything imported will be bundled into that page's script, which is
built into the public folder and referenced in the document head when
you visit that page. This will be better documented later. Closes issue
#15.

### Patch Changes

-   772708e: init changesets

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>

docs/package.json

@@ -13,11 +13,11 @@
     "@hono/node-server": "^1.2.0",
     "highlight.js": "^11.8.0",
     "hono": "^3.7.5",
-    "hwy": "0.4.0-beta.38"
+    "hwy": "0.4.0"
   },
   "devDependencies": {
-    "@hwy-js/build": "0.4.0-beta.38",
-    "@hwy-js/dev": "0.4.0-beta.38",
+    "@hwy-js/build": "0.4.0",
+    "@hwy-js/dev": "0.4.0",
     "@types/node": "^20.8.3",
     "@types/nprogress": "^0.2.1",
     "htmx.org": "^1.9.6",

packages/build/CHANGELOG.md

@@ -1,5 +1,33 @@
 # @hwy-js/build
 
+## 0.4.0
+
+### Minor Changes
+
+- 772708e: First off, huge shoutout to @jharrell for his debugging and research assistance on this PR related to adding Cloudflare Pages support! Thank you!
+
+  Cloudflare Pages is now supported! Closes issue #6.
+
+  Added changesets. Closes issue #14.
+
+  Adds a hwy.config.ts / hwy.config.js file to the root of your project for setting up dev settings and deployment target, and probably other things in the future. As annoying as config files are, this simplifies a lot of things and is not too much to ask for a framework.
+
+  Removes a lot of complexity / variance in build commands and deploy target hacks, as now we can just read the deployment target from the Hwy config and handle everything in Hwy's centralized build step.
+
+  Adds a new @hwy-js/build package, splitting up the live refresh stuff (stays in @hwy-js/dev) from the build stuff.
+
+  In your src/main.tsx file:
+
+  {hwyDev?.DevLiveRefreshScript()} is now just <DevLiveRefreshScript />
+  <ClientEntryScript /> is now <ClientScripts activePathData={activePathData} />. This is to enable the new client scripts functionality mentioned below.
+  Added an option to ship client-side JS (including from TS files if you want) by adding a sibling page-name.client.ts or page-name.client.js file to your page. This becomes basically global JS for that page, and anything imported will be bundled into that page's script, which is built into the public folder and referenced in the document head when you visit that page. This will be better documented later. Closes issue #15.
+
+### Patch Changes
+
+- 772708e: rmv rmSync instance, not really necessary
+- 772708e: init changesets
+- 772708e: tweak build step, auto read latest version in create-hwy
+
 ## 0.4.0-beta.38
 
 ## 0.4.0-beta.37

packages/build/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hwy-js/build",
-  "version": "0.4.0-beta.38",
+  "version": "0.4.0",
   "author": {
     "name": "Samuel J. Cook"
   },

packages/core/CHANGELOG.md

@@ -1,5 +1,32 @@
 # hwy
 
+## 0.4.0
+
+### Minor Changes
+
+- 772708e: First off, huge shoutout to @jharrell for his debugging and research assistance on this PR related to adding Cloudflare Pages support! Thank you!
+
+  Cloudflare Pages is now supported! Closes issue #6.
+
+  Added changesets. Closes issue #14.
+
+  Adds a hwy.config.ts / hwy.config.js file to the root of your project for setting up dev settings and deployment target, and probably other things in the future. As annoying as config files are, this simplifies a lot of things and is not too much to ask for a framework.
+
+  Removes a lot of complexity / variance in build commands and deploy target hacks, as now we can just read the deployment target from the Hwy config and handle everything in Hwy's centralized build step.
+
+  Adds a new @hwy-js/build package, splitting up the live refresh stuff (stays in @hwy-js/dev) from the build stuff.
+
+  In your src/main.tsx file:
+
+  {hwyDev?.DevLiveRefreshScript()} is now just <DevLiveRefreshScript />
+  <ClientEntryScript /> is now <ClientScripts activePathData={activePathData} />. This is to enable the new client scripts functionality mentioned below.
+  Added an option to ship client-side JS (including from TS files if you want) by adding a sibling page-name.client.ts or page-name.client.js file to your page. This becomes basically global JS for that page, and anything imported will be bundled into that page's script, which is built into the public folder and referenced in the document head when you visit that page. This will be better documented later. Closes issue #15.
+
+### Patch Changes
+
+- 772708e: rm console log
+- 772708e: init changesets
+
 ## 0.4.0-beta.38
 
 ## 0.4.0-beta.37

packages/core/package.json

@@ -1,6 +1,6 @@
 {
   "name": "hwy",
-  "version": "0.4.0-beta.38",
+  "version": "0.4.0",
   "author": {
     "name": "Samuel J. Cook"
   },

packages/create-hwy/CHANGELOG.md

@@ -1,5 +1,33 @@
 # create-hwy
 
+## 0.4.0
+
+### Minor Changes
+
+- 772708e: First off, huge shoutout to @jharrell for his debugging and research assistance on this PR related to adding Cloudflare Pages support! Thank you!
+
+  Cloudflare Pages is now supported! Closes issue #6.
+
+  Added changesets. Closes issue #14.
+
+  Adds a hwy.config.ts / hwy.config.js file to the root of your project for setting up dev settings and deployment target, and probably other things in the future. As annoying as config files are, this simplifies a lot of things and is not too much to ask for a framework.
+
+  Removes a lot of complexity / variance in build commands and deploy target hacks, as now we can just read the deployment target from the Hwy config and handle everything in Hwy's centralized build step.
+
+  Adds a new @hwy-js/build package, splitting up the live refresh stuff (stays in @hwy-js/dev) from the build stuff.
+
+  In your src/main.tsx file:
+
+  {hwyDev?.DevLiveRefreshScript()} is now just <DevLiveRefreshScript />
+  <ClientEntryScript /> is now <ClientScripts activePathData={activePathData} />. This is to enable the new client scripts functionality mentioned below.
+  Added an option to ship client-side JS (including from TS files if you want) by adding a sibling page-name.client.ts or page-name.client.js file to your page. This becomes basically global JS for that page, and anything imported will be bundled into that page's script, which is built into the public folder and referenced in the document head when you visit that page. This will be better documented later. Closes issue #15.
+
+### Patch Changes
+
+- 772708e: update ClientEntryScript to ClientScripts
+- 772708e: init changesets
+- 772708e: tweak build step, auto read latest version in create-hwy
+
 ## 0.4.0-beta.38
 
 ### Patch Changes

packages/create-hwy/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-hwy",
-  "version": "0.4.0-beta.38",
+  "version": "0.4.0",
   "author": {
     "name": "Samuel J. Cook"
   },

packages/dev/CHANGELOG.md

@@ -1,5 +1,31 @@
 # @hwy-js/dev
 
+## 0.4.0
+
+### Minor Changes
+
+- 772708e: First off, huge shoutout to @jharrell for his debugging and research assistance on this PR related to adding Cloudflare Pages support! Thank you!
+
+  Cloudflare Pages is now supported! Closes issue #6.
+
+  Added changesets. Closes issue #14.
+
+  Adds a hwy.config.ts / hwy.config.js file to the root of your project for setting up dev settings and deployment target, and probably other things in the future. As annoying as config files are, this simplifies a lot of things and is not too much to ask for a framework.
+
+  Removes a lot of complexity / variance in build commands and deploy target hacks, as now we can just read the deployment target from the Hwy config and handle everything in Hwy's centralized build step.
+
+  Adds a new @hwy-js/build package, splitting up the live refresh stuff (stays in @hwy-js/dev) from the build stuff.
+
+  In your src/main.tsx file:
+
+  {hwyDev?.DevLiveRefreshScript()} is now just <DevLiveRefreshScript />
+  <ClientEntryScript /> is now <ClientScripts activePathData={activePathData} />. This is to enable the new client scripts functionality mentioned below.
+  Added an option to ship client-side JS (including from TS files if you want) by adding a sibling page-name.client.ts or page-name.client.js file to your page. This becomes basically global JS for that page, and anything imported will be bundled into that page's script, which is built into the public folder and referenced in the document head when you visit that page. This will be better documented later. Closes issue #15.
+
+### Patch Changes
+
+- 772708e: init changesets
+
 ## 0.4.0-beta.38
 
 ## 0.4.0-beta.37

packages/dev/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hwy-js/dev",
-  "version": "0.4.0-beta.38",
+  "version": "0.4.0",
   "author": {
     "name": "Samuel J. Cook"
   },