We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://developers.cloudflare.com/workers/frameworks/framework-guides/nextjs/
In step 2, the final suggested line is: experimental_assets = { directory = ".worker-next/assets", binding = "ASSETS" }
experimental_assets = { directory = ".worker-next/assets", binding = "ASSETS" }
when it should in fact be assets = { directory = ".worker-next/assets", binding = "ASSETS" }
assets = { directory = ".worker-next/assets", binding = "ASSETS" }
In step 3, the instructions suggest adding to package.json :
package.json
"deploy:worker": "npm run build:worker && wrangler deploy"
But this is later referred to incorrectly twice:
First in the last bullet immediately following the package.json instructions:
npm run deploy: Builds your app, and then deploys it to Cloudflare
Then again in step 6:
deploy via the command line: Terminal window npm run deploy
npm run deploy
No response
The text was updated successfully, but these errors were encountered:
irvinebroque
mikenomitch
GregBrimble
WalshyDev
ToriLindsay
No branches or pull requests
Existing documentation URL(s)
https://developers.cloudflare.com/workers/frameworks/framework-guides/nextjs/
What changes are you suggesting?
In step 2, the final suggested line is:
experimental_assets = { directory = ".worker-next/assets", binding = "ASSETS" }
when it should in fact be
assets = { directory = ".worker-next/assets", binding = "ASSETS" }
In step 3, the instructions suggest adding to
package.json
:But this is later referred to incorrectly twice:
First in the last bullet immediately following the
package.json
instructions:Then again in step 6:
Additional information
No response
The text was updated successfully, but these errors were encountered: