Version Packages

[github-actions[bot]]

This PR was opened by the Changesets release 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 is now . 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 is now . 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 is now . 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 is now . 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

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
hwy-docs	❌ Failed (Inspect)			Oct 21, 2023 8:44pm