-
Notifications
You must be signed in to change notification settings - Fork 734
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: align publishing sites asset keys with Wrangler 1 #277
fix: align publishing sites asset keys with Wrangler 1 #277
Conversation
🦋 Changeset detectedLatest commit: 40969cb The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
8c1c3fd
to
a3101a1
Compare
a3101a1
to
d344be9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a couple of notes, but this looks good to me. Thank you for fleshing this out! Important for people moving projects over, I appreciate that you did the command line args too.
d344be9
to
b83b9eb
Compare
- Use the same hashing strategy for asset keys (xxhash64) - Include the full path (from cwd) in the asset key - Match include and exclude patterns against full path (from cwd) - Validate that the asset key is not over 512 bytes long
b83b9eb
to
40969cb
Compare
I'm not sure if this has to do with this merge, but I just updated 0.0.6 to 0.0.15 and npm is unable to build xxhash-addon (and that package looks a bit unmaintained, tbh):
|
I got the same error when trying to use the Windows 2022 Server runner in our Github Actions. Your machine needs to have the necessary compilers installed on your machine (Unix based machines tend to have these already). For Windows you can follow the instructions here: https://github.com/nodejs/node-gyp#on-windows. I'll have a look around and see if there is an alternative xxhash implementation we can use that doesn't require node-gyp. But when I implemented this last month, I did not find a suitable one. In the long run, we should probably move away from xxhash and use a hashing algorithm that is supported by node.js out of the box. The downside of doing this right now is that any assets that were previously uploaded to Sites would get new hashes and so would need to be uploaded and stored again. |
Perhaps we can try https://www.npmjs.com/package/xxhash-wasm |
Builds on top of #270.