You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We had a bug where we were generating asset manifest keys incorrectly if we ran wrangler from a different path to `wrangler.toml`. This fixes the generation of said keys, and adds a test for it.
Fixes#1235
threepointone
changed the title
🐛 BUG: site.bucket should be resolved relative to wrangler.toml
🐛 BUG: site manifest isn't generated correctly when wrangler dev/publish is run in a non-root directory
Jun 12, 2022
We had a bug where we were generating asset manifest keys incorrectly if we ran wrangler from a different path to `wrangler.toml`. This fixes the generation of said keys, and adds a test for it.
Fixes#1235
We had a bug where we were generating asset manifest keys incorrectly if we ran wrangler from a different path to `wrangler.toml`. This fixes the generation of said keys, and adds a test for it.
Fixes#1235
What version of
Wrangler
are you using?2.0.9
What operating system are you using?
Mac
Describe the Bug
cd examples/legacy-site-app && wrangler dev
localhost:8787
and the page loads as expectedcd workers-site && npx wrangler dev index.js
localhost:8787
and you'll see a messagecould not find index.html in your content namespace
I think this is because we don't modifysite.bucket
to be resolved relative to the path towrangler.toml
.The text was updated successfully, but these errors were encountered: