Uh oh!
There was an error while loading. Please reload this page.
[cli] Print notice on CLI startup when detecting an outdated version - #701
Conversation
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
The latest updates on your projects. Learn more about Vercel for GitHub.
|
🦋 Changeset detectedLatest commit: 3d0d66e The changes in this PR will be included in the next version bump. This PR includes changesets to release 4 packages
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 |
🧪 E2E Test Results❌ Some tests failed Summary
❌ Failed Tests🌍 Community Worlds (11 failed)mongodb (1 failed):
starter (9 failed):
turso (1 failed):
Details by Category✅ ▲ Vercel Production
✅ 💻 Local Development
✅ 📦 Local Production
✅ 🐘 Local Postgres
✅ 🪟 Windows
❌ 🌍 Community Worlds
|
📊 Benchmark Results
workflow with no steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Next.js (Turbopack) | Express | Nitro workflow with 1 step💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro | Express | Next.js (Turbopack) workflow with 10 sequential steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro | Express | Next.js (Turbopack) Promise.all with 10 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Next.js (Turbopack) | Nitro Promise.all with 25 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro | Express | Next.js (Turbopack) Promise.race with 10 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Nitro | Express | Next.js (Turbopack) Promise.race with 25 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Next.js (Turbopack) | Nitro Stream Benchmarks(includes TTFB metrics)workflow with stream💻 Local Development
▲ Production (Vercel)
🔍 Observability: Next.js (Turbopack) | Nitro | Express SummaryFastest Framework by WorldWinner determined by most benchmark wins
Fastest World by FrameworkWinner determined by most benchmark wins
Column Definitions
Worlds:
|
Uh oh!
There was an error while loading. Please reload this page.
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
…me using `createRequire` with a relative path. When bundled by Vite/SvelteKit for SSR, the relative path becomes invalid because the output file is at a different location than the source file, causing a MODULE_NOT_FOUND error. The fix uses `import.meta.resolve()` which provides correct path resolution even in bundled environments. This commit fixes the issue reported at packages/world-local/src/init.ts:1-18 ## SvelteKit build fails: Cannot find module '../package.json' in bundled SSR code **What fails:** During SvelteKit SSR build, the `vite build` command fails with error: `Error: Cannot find module '../package.json'` in compiled code at `.svelte-kit/output/server/chunks/step-handler.js:1711:21` **How to reproduce:** ```bash cd workbench/sveltekit pnpm run build ``` During the "rendering chunks" phase, when Vite bundles the SSR output, the compiled code attempts to require `../package.json` which fails because the relative path from the bundled output file location is invalid. **Result:** ``` Error: Cannot find module '../package.json' Require stack: - /vercel/path0/workbench/sveltekit/.svelte-kit/output/server/chunks/step-handler.js ``` **Root cause:** The `packages/world-local/src/init.ts` file uses `createRequire(import.meta.url)` with a relative path `../package.json` to load the package.json file. When Rollup/Vite bundles this code for SSR, the relative path becomes invalid because the output file is at a different location than the source file. **Solution:** Use `import.meta.resolve()` which provides proper module path resolution even in bundled environments. Falls back to `createRequire()` for compatibility with test environments where `import.meta.resolve()` may not be available. Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
Uh oh!
There was an error while loading. Please reload this page.
Co-authored-by: vercel[bot] <35613825+vercel[bot]@users.noreply.github.com>
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
Signed-off-by: Peter Wielander <mittgfu@gmail.com>
This superseeds #657, which tried to use an npm plugin for this job, but was ugly and didn't work with pre-release versions, so I had claude implement it instead.
Essentially:
@workflow/cliglobally separately fromworkflow, sincep i workflow@latestwouldn't resolve the update warning, but this seems like a minor concern.