fix(create-cloudflare): bump vitest-pool-workers version on the templates#7827
fix(create-cloudflare): bump vitest-pool-workers version on the templates#7827andyjessop merged 12 commits intomainfrom
Conversation
🦋 Changeset detectedLatest commit: 583d551 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 |
|
A wrangler prerelease is available for testing. You can install this latest build in your project with: npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/12888773890/npm-package-wrangler-7827You can reference the automatically updated head of this PR with: npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/prs/7827/npm-package-wrangler-7827Or you can use npx https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/12888773890/npm-package-wrangler-7827 dev path/to/script.jsAdditional artifacts:cloudflare-workers-bindings-extension: wget https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/12888773890/npm-package-cloudflare-workers-bindings-extension-7827 -O ./cloudflare-workers-bindings-extension.0.0.0-v566bdc5be.vsix && code --install-extension ./cloudflare-workers-bindings-extension.0.0.0-v566bdc5be.vsixcreate-cloudflare: npx https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/12888773890/npm-package-create-cloudflare-7827 --no-auto-update@cloudflare/kv-asset-handler: npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/12888773890/npm-package-cloudflare-kv-asset-handler-7827miniflare: npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/12888773890/npm-package-miniflare-7827@cloudflare/pages-shared: npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/12888773890/npm-package-cloudflare-pages-shared-7827@cloudflare/unenv-preset: npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/12888773890/npm-package-cloudflare-unenv-preset-7827@cloudflare/vite-plugin: npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/12888773890/npm-package-cloudflare-vite-plugin-7827@cloudflare/vitest-pool-workers: npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/12888773890/npm-package-cloudflare-vitest-pool-workers-7827@cloudflare/workers-editor-shared: npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/12888773890/npm-package-cloudflare-workers-editor-shared-7827@cloudflare/workers-shared: npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/12888773890/npm-package-cloudflare-workers-shared-7827@cloudflare/workflows-shared: npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/12888773890/npm-package-cloudflare-workflows-shared-7827Note that these links will no longer work once the GitHub Actions artifact expires.
Please ensure constraints are pinned, and |
There was a problem hiding this comment.
this feels like something we should be doing for all C3 starter projects that come accompanied by tests?
There was a problem hiding this comment.
Afaik only hello-world and the experimental hello-world-with-assets template (js/ts) includes some tests. But there is no e2e tests for non-framework experimental templates. Let me see if I can set it up for the assets template 👍🏼
f12136c to
6865673
Compare
0739dc4 to
1d45ce9
Compare
1d45ce9 to
d3e1866
Compare
There was a problem hiding this comment.
I think this will probably break the e2e cleanup scripts—is there a reason this needed to be changed?
There was a problem hiding this comment.
Good catch! That might explains why some e2e tests are failing 😅
We are using prefix + random suffix + template name + language as the project name on the e2e tests and some of the templates end up with a project name more than 58 chars. So I was thinking if we can shrink the prefix a bit to save a few chars.. but maybe I should just trim it.
|
@CarmenPopoviciu @penalosa This is ready for review again 👍🏼 |
| { | ||
| template: "scheduled", | ||
| variants: ["TypeScript", "JavaScript"], | ||
| variants: ["ts", "js"], |
There was a problem hiding this comment.
All the variant name is changed as
- It is now passed as
--lang [lang]instead of going through a prompt and have the test script figure out the right answer. - They are part of the project name and might become too long depending on the template name. It should be less likly to be over 58 chars now.
| promptHandlers: [ | ||
| { | ||
| matcher: /Which language do you want to use\?/, | ||
| input: { | ||
| type: "select", | ||
| target: variant, | ||
| }, | ||
| }, | ||
| ], |
There was a problem hiding this comment.
We are now passing the --lang arg directly instead of trying to answer the prompt.
| const gitignorePath = join(project.path, ".gitignore"); | ||
| expect(gitignorePath).toExist(); | ||
|
|
There was a problem hiding this comment.
The asset-only template has no .gitignore. I could have add an options to skip this check but I think we shouldn't assume .gitignore exists on all template especially when the git setup on c3 is optional.
| if (config.main) { | ||
| expect(join(project.path, config.main)).toExist(); | ||
| } |
There was a problem hiding this comment.
The asset-only template has no main file 😅
Fixes #7815.