Skip to content

Commit

Permalink
lock and changeset
Browse files Browse the repository at this point in the history
  • Loading branch information
sjc5 committed Oct 21, 2023
1 parent 8e4ca61 commit a4f77c3
Show file tree
Hide file tree
Showing 2 changed files with 20 additions and 10 deletions.
24 changes: 17 additions & 7 deletions .changeset/shy-nails-cover.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,10 +5,20 @@
"@hwy-js/dev": minor
---

- Cloudflare Pages is now supported!
- 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.
- `{hwyDev?.DevLiveRefreshScript()}` is now `<DevLiveRefreshScript />`
- `<ClientEntryScript />` is now `<ClientScripts activePathData={activePathData} />`
- 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.
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.
6 changes: 3 additions & 3 deletions pnpm-lock.yaml

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

0 comments on commit a4f77c3

Please sign in to comment.