f3ef4e99b0
We want to make sure that our examples are not breaking. We don't want to be slowed down by broken 3rd party packages, but we need to ensure that examples covering next.js features are always green. Added as a standalone workflow that doesn't parallelize. It will just run on a cron schedule, so we can check for current status. We can add Slack ping later if we need to. The workflow tests just that our examples can build, so mostly TS issues. We could definitely follow up with actual tests, but that is not as low-hanging. --------- Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com> Co-authored-by: Tim Neutkens <tim@timneutkens.nl> |
||
|---|---|---|
| .. | ||
| pages | ||
| utils | ||
| .gitignore | ||
| package.json | ||
| README.md | ||
| tsconfig.json | ||
| worker.ts | ||
WebWorker example
This example shows how to run code in WebWorkers by utilizing webpack 5.
Deploy your own
Deploy the example using Vercel or preview live with StackBlitz
How to use
Execute create-next-app with npm, Yarn, or pnpm to bootstrap the example:
npx create-next-app --example with-web-worker with-web-worker-app
yarn create next-app --example with-web-worker with-web-worker-app
pnpm create next-app --example with-web-worker with-web-worker-app
Deploy it to the cloud with Vercel (Documentation).