Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
46 commits
Select commit Hold shift + click to select a range
8c5ba31
feat(cli): add alchemy and improve cli tooling and structure
AmanVarshney01 Aug 15, 2025
0ec0301
add advanced cookie attributes in better auth config
AmanVarshney01 Aug 16, 2025
f807e00
fix imports
AmanVarshney01 Aug 16, 2025
2d8fd0a
add server deploy in display config
AmanVarshney01 Aug 16, 2025
34505f3
update logic
AmanVarshney01 Aug 16, 2025
c017331
convert to async fs and tinyglobby
AmanVarshney01 Aug 17, 2025
d2c197a
update
AmanVarshney01 Aug 17, 2025
29eb171
update
AmanVarshney01 Aug 17, 2025
54af26d
update
AmanVarshney01 Aug 17, 2025
5b7ffa9
update
AmanVarshney01 Aug 17, 2025
0af501c
remove useless comments
AmanVarshney01 Aug 18, 2025
8c98333
update
AmanVarshney01 Aug 18, 2025
cdad96e
refactor next setup
AmanVarshney01 Aug 18, 2025
690c2e8
fix
AmanVarshney01 Aug 18, 2025
8a8952e
format all templates with biome
AmanVarshney01 Aug 18, 2025
971fe8f
add cloudflare types file
AmanVarshney01 Aug 18, 2025
df5bd78
update
AmanVarshney01 Aug 18, 2025
cae5650
rename workers deploy to wrangler
AmanVarshney01 Aug 18, 2025
8ddba0f
add node compatibility
AmanVarshney01 Aug 18, 2025
011f035
refactor worker code
AmanVarshney01 Aug 18, 2025
8be9c73
improve biome logic
AmanVarshney01 Aug 18, 2025
ed425ad
add convex codegen
AmanVarshney01 Aug 18, 2025
9a556f9
fix wrangler template path
AmanVarshney01 Aug 18, 2025
63a3fcd
ok
AmanVarshney01 Aug 18, 2025
75585bb
update something
AmanVarshney01 Aug 18, 2025
15112eb
fix
AmanVarshney01 Aug 18, 2025
205775b
remove .dev.vars
AmanVarshney01 Aug 19, 2025
dccfacf
fix
AmanVarshney01 Aug 19, 2025
5d0cd23
fix d1 setup
AmanVarshney01 Aug 19, 2025
dd57289
add canary release script
AmanVarshney01 Aug 19, 2025
0b6f540
fix template logic
AmanVarshney01 Aug 19, 2025
ee4c69e
update canary release
AmanVarshney01 Aug 19, 2025
ec2bbe3
fix lock
AmanVarshney01 Aug 19, 2025
f1912e9
update site
AmanVarshney01 Aug 19, 2025
88769d6
update flags logic
AmanVarshney01 Aug 19, 2025
4a10404
use convex in web for testimonials, sponsors and showcase
AmanVarshney01 Aug 19, 2025
7db03e6
fix post install notes
AmanVarshney01 Aug 19, 2025
9bb4f33
organize code
AmanVarshney01 Aug 20, 2025
20c8e95
update docs
AmanVarshney01 Aug 20, 2025
0a90621
fix prisma setup for drizzle
AmanVarshney01 Aug 20, 2025
38a6c01
add temp wrangler.jsonc
AmanVarshney01 Aug 20, 2025
41540a8
fix yolo mode
AmanVarshney01 Aug 20, 2025
79a0519
fix d1 setup
AmanVarshney01 Aug 20, 2025
2ec142a
fix
AmanVarshney01 Aug 20, 2025
0ed8c9e
fix docs
AmanVarshney01 Aug 20, 2025
472e841
add temp validation for nextjs and react router
AmanVarshney01 Aug 20, 2025
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 0 additions & 8 deletions .changeset/README.md

This file was deleted.

11 changes: 0 additions & 11 deletions .changeset/config.json

This file was deleted.

674 changes: 674 additions & 0 deletions .cursor/rules/convex_rules.mdc

Large diffs are not rendered by default.

108 changes: 108 additions & 0 deletions .cursor/rules/use-bun-instead-of-node-vite-npm-pnpm.mdc
Original file line number Diff line number Diff line change
@@ -0,0 +1,108 @@
---
alwaysApply: true
---
Default to using Bun instead of Node.js.

- Use `bun <file>` instead of `node <file>` or `ts-node <file>`
- Use `bun test` instead of `jest` or `vitest`
- Use `bun build <file.html|file.ts|file.css>` instead of `webpack` or `esbuild`
- Use `bun install` instead of `npm install` or `yarn install` or `pnpm install`
- Use `bun run <script>` instead of `npm run <script>` or `yarn run <script>` or `pnpm run <script>`
- Bun automatically loads .env, so don't use dotenv.

## APIs

- `Bun.serve()` supports WebSockets, HTTPS, and routes. Don't use `express`.
- `bun:sqlite` for SQLite. Don't use `better-sqlite3`.
- `Bun.redis` for Redis. Don't use `ioredis`.
- `Bun.sql` for Postgres. Don't use `pg` or `postgres.js`.
- `WebSocket` is built-in. Don't use `ws`.
- Prefer `Bun.file` over `node:fs`'s readFile/writeFile
- Bun.$`ls` instead of execa.

## Testing

Use `bun test` to run tests.

```ts#index.test.ts
import { test, expect } from "bun:test";

test("hello world", () => {
expect(1).toBe(1);
});
```

## Frontend

Use HTML imports with `Bun.serve()`. Don't use `vite`. HTML imports fully support React, CSS, Tailwind.

Server:

```ts#index.ts
import index from "./index.html"

Bun.serve({
routes: {
"/": index,
"/api/users/:id": {
GET: (req) => {
return new Response(JSON.stringify({ id: req.params.id }));
},
},
},
// optional websocket support
websocket: {
open: (ws) => {
ws.send("Hello, world!");
},
message: (ws, message) => {
ws.send(message);
},
close: (ws) => {
// handle close
}
},
development: {
hmr: true,
console: true,
}
})
```
Comment thread
coderabbitai[bot] marked this conversation as resolved.
Resolved

HTML files can import .tsx, .jsx or .js files directly and Bun's bundler will transpile & bundle automatically. `<link>` tags can point to stylesheets and Bun's CSS bundler will bundle.

```html#index.html
<html>
<body>
<h1>Hello, world!</h1>
<script type="module" src="./frontend.tsx"></script>
</body>
</html>
```

With the following `frontend.tsx`:

```tsx#frontend.tsx
import React from "react";

// import .css files directly and it works
import './index.css';

import { createRoot } from "react-dom/client";

const root = createRoot(document.body);

export default function Frontend() {
return <h1>Hello, world!</h1>;
}

root.render(<Frontend />);
```

Then, run index.ts

```sh
bun --hot ./index.ts
```

For more information, read the Bun API docs in `node_modules/bun-types/docs/**.md`.
30 changes: 0 additions & 30 deletions .github/workflows/preview.yaml

This file was deleted.

36 changes: 18 additions & 18 deletions .github/workflows/release.yaml
Original file line number Diff line number Diff line change
@@ -1,17 +1,12 @@
name: Release

permissions:
contents: write

on:
push:
branches:
- main
- beta
paths:
- "apps/cli/**"
- ".changeset/**"
- "package.json"
- "bun.lock"

concurrency: ${{ github.workflow }}-${{ github.ref }}
tags:
- 'v*'

jobs:
release:
Expand All @@ -30,14 +25,19 @@ jobs:
- name: Install Dependencies
run: bun install --frozen-lockfile

- name: Create Release Pull Request or Publish
id: changesets
uses: changesets/action@v1
with:
publish: bun run publish-packages
- name: Build CLI
run: bun run build:cli
env:
BTS_TELEMETRY: 1
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
POSTHOG_API_KEY: ${{ secrets.POSTHOG_API_KEY }}
POSTHOG_HOST: ${{ secrets.POSTHOG_HOST }}
POSTHOG_HOST: ${{ secrets.POSTHOG_HOST }}

- name: Generate Changelog
run: bun run release
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

- name: Publish CLI to NPM
run: cd apps/cli && bun publish --access public
env:
NPM_CONFIG_TOKEN: ${{ secrets.NPM_TOKEN }}
Comment on lines +41 to +43

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Use the standard env var for npm auth in CI (NODE_AUTH_TOKEN)

NPM_CONFIG_TOKEN isn’t a standard npm/bun publish auth variable. Publishing typically uses NODE_AUTH_TOKEN. Use that to avoid auth failures.

-      - name: Publish CLI to NPM
-        run: cd apps/cli && bun publish --access public
-        env:
-          NPM_CONFIG_TOKEN: ${{ secrets.NPM_TOKEN }}
+      - name: Publish CLI to NPM
+        run: cd apps/cli && bun publish --access public
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}

If you rely on a custom .npmrc, ensure it’s present and points to the correct registry.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
run: cd apps/cli && bun publish --access public
env:
NPM_CONFIG_TOKEN: ${{ secrets.NPM_TOKEN }}
- name: Publish CLI to NPM
run: cd apps/cli && bun publish --access public
env:
NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
🧰 Tools
🪛 YAMLlint (1.37.1)

[error] 43-43: no new line character at the end of file

(new-line-at-end-of-file)

🤖 Prompt for AI Agents
In .github/workflows/release.yaml around lines 41–43, the workflow sets the
nonstandard NPM_CONFIG_TOKEN for publishing; replace that env var with the
standard NODE_AUTH_TOKEN (e.g. env: NODE_AUTH_TOKEN: ${{ secrets.NODE_AUTH_TOKEN
}} or map it to your existing secret name if you prefer: ${{ secrets.NPM_TOKEN
}} -> NODE_AUTH_TOKEN) so bun/npm publish uses the expected CI auth token, and
ensure any custom .npmrc referenced by the job is committed and points to the
correct registry.

3 changes: 2 additions & 1 deletion apps/cli/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -66,7 +66,8 @@ Options:
--install Install dependencies
--no-install Skip installing dependencies
--db-setup <setup> Database setup (turso, d1, neon, supabase, prisma-postgres, mongodb-atlas, docker, none)
--web-deploy <setup> Web deployment (workers, none)
--web-deploy <setup> Web deployment (workers, alchemy, none)
--server-deploy <setup> Server deployment (workers, alchemy, none)
--backend <framework> Backend framework (hono, express, elysia, next, convex, fastify, none)
--runtime <runtime> Runtime (bun, node, workers, none)
--api <type> API type (trpc, orpc, none)
Expand Down
9 changes: 6 additions & 3 deletions apps/cli/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,8 @@
"dev": "tsdown --watch",
"check-types": "tsc --noEmit",
"check": "biome check --write .",
"test": "bun run build && vitest --ui",
"test": "bun run build && vitest run",
"test:ui": "bun run build && vitest --ui",
"test:with-build": "bun run build && WITH_BUILD=1 vitest --ui",
"prepublishOnly": "npm run build"
},
Expand All @@ -63,22 +64,24 @@
}
},
"dependencies": {
"@biomejs/js-api": "^3.0.0",
"@biomejs/wasm-nodejs": "^2.2.0",
"@clack/prompts": "^0.11.0",
"consola": "^3.4.2",
"execa": "^9.6.0",
"fs-extra": "^11.3.1",
"globby": "^14.1.0",
"gradient-string": "^3.0.0",
"handlebars": "^4.7.8",
"jsonc-parser": "^3.3.1",
"picocolors": "^1.1.1",
"tinyglobby": "^0.2.14",
"trpc-cli": "^0.10.2",
"ts-morph": "^26.0.0",
"zod": "^4.0.17"
},
"devDependencies": {
"@types/fs-extra": "^11.0.4",
"@types/node": "^24.2.1",
"@types/node": "^24.3.0",
"@vitest/ui": "^3.2.4",
"tsdown": "^0.14.1",
"typescript": "^5.9.2",
Expand Down
55 changes: 38 additions & 17 deletions apps/cli/src/constants.ts
Original file line number Diff line number Diff line change
Expand Up @@ -7,25 +7,37 @@ const __filename = fileURLToPath(import.meta.url);
const distPath = path.dirname(__filename);
export const PKG_ROOT = path.join(distPath, "../");

export const DEFAULT_CONFIG: ProjectConfig = {
export const DEFAULT_CONFIG_BASE = {
projectName: "my-better-t-app",
projectDir: path.resolve(process.cwd(), "my-better-t-app"),
relativePath: "my-better-t-app",
frontend: ["tanstack-router"],
database: "sqlite",
orm: "drizzle",
frontend: ["tanstack-router"] as const,
database: "sqlite" as const,
orm: "drizzle" as const,
auth: true,
addons: ["turborepo"],
examples: [],
addons: ["turborepo"] as const,
examples: [] as const,
git: true,
packageManager: getUserPkgManager(),
install: true,
dbSetup: "none",
backend: "hono",
runtime: "bun",
api: "trpc",
webDeploy: "none",
};
dbSetup: "none" as const,
backend: "hono" as const,
runtime: "bun" as const,
api: "trpc" as const,
webDeploy: "none" as const,
serverDeploy: "none" as const,
} as const;

export function getDefaultConfig(): ProjectConfig {
return {
...DEFAULT_CONFIG_BASE,
projectDir: path.resolve(process.cwd(), DEFAULT_CONFIG_BASE.projectName),
packageManager: getUserPkgManager(),
frontend: [...DEFAULT_CONFIG_BASE.frontend],
addons: [...DEFAULT_CONFIG_BASE.addons],
examples: [...DEFAULT_CONFIG_BASE.examples],
};
}

export const DEFAULT_CONFIG = getDefaultConfig();

export const dependencyVersionMap = {
"better-auth": "^1.3.4",
Expand Down Expand Up @@ -106,7 +118,8 @@ export const dependencyVersionMap = {
"convex-nuxt": "0.1.5",
"convex-vue": "^0.1.5",

"@tanstack/svelte-query": "^5.74.4",
"@tanstack/svelte-query": "^5.85.3",
"@tanstack/svelte-query-devtools": "^5.85.3",
Comment on lines +121 to +122

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

🧩 Analysis chain

Devtools entries: ensure they are added as devDependencies (not production deps).

Given these are tooling/dev-only, verify the scaffolding places:

  • @tanstack/svelte-query-devtools and @tanstack/solid-router-devtools under devDependencies.

Use this quick check across templates:

Also applies to: 121-121


🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "🔍 Where are devtools referenced in templates?"
rg -n -C2 -P '"@tanstack/(svelte-query-devtools|solid-router-devtools)"' apps/cli/templates

echo
echo "🔍 package.json(.hbs) blocks that define devDependencies:"
rg -n -C1 -P '"devDependencies"\s*:\s*\{' apps/cli/templates | sed 's/^/• /'

Length of output: 4179


🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "🔍 Checking for @tanstack/svelte-query-devtools in Svelte template package.json.hbs:"
rg -n -C2 '"@tanstack/svelte-query-devtools"' apps/cli/templates/frontend/svelte/package.json.hbs || echo "→ Not found in Svelte template"

echo
echo "🔍 Checking for @tanstack/solid-router-devtools in Solid template package.json.hbs:"
rg -n -C2 '"@tanstack/solid-router-devtools"' apps/cli/templates/frontend/solid/package.json.hbs || echo "→ Not found in Solid template"

Length of output: 722


Ensure devtools entries live under devDependencies

The CLI’s constants.ts currently lists the devtools packages as production dependencies, and none of the package.json.hbs templates include them in their devDependencies blocks. This will break the generated projects (imports of Devtools in the route templates won’t resolve).

• In apps/cli/src/constants.ts – move

"@tanstack/svelte-query-devtools": "^5.85.3",
"@tanstack/solid-router-devtools": "^5.85.3",

out of the dependencies object and into the devDependencies object.

• In apps/cli/templates/frontend/svelte/package.json.hbs – under the "devDependencies": { … } block, add:

  "@tanstack/svelte-query-devtools": "{{constants.versions['@tanstack/svelte-query-devtools']}}"

• In apps/cli/templates/frontend/solid/package.json.hbs – under the "devDependencies": { … } block, add:

  "@tanstack/solid-query-devtools": "{{constants.versions['@tanstack/solid-query-devtools']}}",
  "@tanstack/solid-router-devtools": "{{constants.versions['@tanstack/solid-router-devtools']}}"

This aligns the scaffolding with the Devtools imports in __root.tsx.hbs and keeps these packages in devDependencies.

🤖 Prompt for AI Agents
In apps/cli/src/constants.ts around lines 110-111, the devtools packages are
incorrectly listed under dependencies; move "@tanstack/svelte-query-devtools"
and "@tanstack/solid-router-devtools" (and any other devtools entries like
"@tanstack/solid-query-devtools") from the dependencies object into the
devDependencies object so they are generated as devDependencies. Then update
apps/cli/templates/frontend/svelte/package.json.hbs to add the
"@tanstack/svelte-query-devtools" entry inside the "devDependencies" block using
the constants.versions lookup, and update
apps/cli/templates/frontend/solid/package.json.hbs to add
"@tanstack/solid-query-devtools" and "@tanstack/solid-router-devtools" inside
its "devDependencies" block using the constants.versions values so the
scaffolded projects can resolve the Devtools imports.


"@tanstack/vue-query-devtools": "^5.83.0",
"@tanstack/vue-query": "^5.83.0",
Expand All @@ -116,19 +129,27 @@ export const dependencyVersionMap = {

"@tanstack/solid-query": "^5.75.0",
"@tanstack/solid-query-devtools": "^5.75.0",
"@tanstack/solid-router-devtools": "^1.131.25",

wrangler: "^4.23.0",
"@cloudflare/vite-plugin": "^1.9.0",
"@opennextjs/cloudflare": "^1.3.0",
"nitro-cloudflare-dev": "^0.2.2",
"@sveltejs/adapter-cloudflare": "^7.0.4",
"@sveltejs/adapter-cloudflare": "^7.2.1",
"@cloudflare/workers-types": "^4.20250813.0",

Comment on lines +138 to +140

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

🧩 Analysis chain

Cloudflare stack bumps: verify types are picked up via tsconfig

Versions look fine. Since worker types generation was removed from create flow, ensure templates set "types": ["@cloudflare/workers-types"] in tsconfig for Worker runtimes (web and server).

Run:

Expected: tsconfig files for Cloudflare-bound projects reference the workers types explicitly.


🏁 Script executed:

#!/bin/bash
# Check that at least the backend/frontend worker runtimes reference workers-types in tsconfig
rg -n -C2 -P '"types"\s*:\s*\[.*"@cloudflare/workers-types".*\]' --type=json

Length of output: 78


🏁 Script executed:

#!/bin/bash
set -euo pipefail

# 1. Locate all tsconfig files in the repo
echo "🔍 Searching for tsconfig files..."
tsconfigs=$(fd --hidden --type f 'tsconfig*.json')

if [[ -z "$tsconfigs" ]]; then
  echo "⚠️ No tsconfig*.json files found in the repo."
  exit 0
fi

# 2. For each tsconfig, show any references to workers-types and the "types" array
for cfg in $tsconfigs; do
  echo
  echo "=== Checking $cfg ==="
  grep -Hn '"@cloudflare/workers-types"' "$cfg" || echo "— no explicit @cloudflare/workers-types entry"
  echo
  grep -Hn '"types"\s*:' "$cfg" || echo "— no \"types\" array found"
done

Length of output: 10892


Ensure Cloudflare Worker types are declared in your tsconfig templates

Most of the generated tsconfig.json.hbs files don’t include the @cloudflare/workers-types entry under "types", so TypeScript won’t pick up Cloudflare Worker globals when using the new adapter. Please add or extend the types array in each Worker-targeted tsconfig as shown below.

Files to update:

  • apps/cli/templates/frontend/svelte/tsconfig.json.hbs
  • apps/cli/templates/frontend/nuxt/server/tsconfig.json (if you intend to deploy Nuxt on Workers)
  • tsconfig.json (root or any shared config used by Worker projects)

Example diff for tsconfig.json.hbs:

 {
   "compilerOptions": {
-    "types": ["vite/client"]
+    "types": [
+      "vite/client",
+      "@cloudflare/workers-types"
+    ]
   }
 }

Committable suggestion skipped: line range outside the PR's diff.

alchemy: "^0.62.1",
// temporary workaround for alchemy + tanstack start
nitropack: "^2.12.4",

dotenv: "^17.2.1",
Comment on lines +141 to +145

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

🧩 Analysis chain

Sanity-check new packages and the “temporary workaround”

  • alchemy: Please confirm this is the intended CLI/tooling package (name "alchemy") and that ^0.62.x exists and matches your deployment story (to avoid confusion with similarly named SDKs).
  • dotenv: Ensure ^17.x is available and compatible with your minimum Node/Bun targets.
  • nitropack: OK as a temporary workaround; consider tracking it with a TODO + issue link for later removal.

Additionally, consider changing the in-code comment to a TODO with a link to an issue for traceability.


🌐 Web query:

Confirm the following:
1) Is there an npm package named "alchemy" at version 0.62.x that provides the CLI/tooling you intend for deployments here?
2) What is the latest version of "dotenv" and any breaking changes since v16 that would affect typical usage?

💡 Result:

Short answers (checked on Aug 18, 2025):

  1. alchemy (the IaC project)
  • There is an active alchemy repo (sam-goodwin/alchemy) and the project provides an optional CLI for deploy/run (docs describe alchemy deploy / alchemy run). (alchemy.run)
  • The GitHub project has released v0.62.0 / v0.62.1 / v0.62.2 (tags dated Aug 15–17, 2025). (github.com)
  • However, the published npm package currently listed as the package "alchemy" shows v0.60.2 as the npm “version” (last published on/around Aug 11–17, 2025 on the npm page). That means the v0.62.x code is present on GitHub releases but (as of Aug 18, 2025) you may not find v0.62.x under the npm “latest” tag yet. (npmjs.com, github.com)

What that implies for deployments

  • If you need the CLI/tooling from v0.62.x right now, you can:
    • Use the GitHub release/tag (install from the git URL / tag), or
    • Wait for the author to publish v0.62.x to the npm registry and then npm install normally.
  • If you want, tell me whether you prefer “install from GitHub” or to wait and I’ll give the exact install command and any caveats.
  1. dotenv — latest & breaking changes since v16
  • Latest (checked Aug 18, 2025): dotenv has releases in the 17.x line (sources listing latest as 17.2.1). (Multiple package-index views show 17.x as the latest line; older 16.x pages are still visible in the registry docs.) (socket.dev, security.snyk.io)

Breaking / noteworthy changes since v16 (practical effects)

  • The big behavioral changes that affect typical usage were introduced in v15 and continued through v16:
    • Inline comments: the parser treats # as the start of a comment (unless the value is quoted). If you have values that include # (e.g. SECRET_HASH=abc#123), you must quote them: SECRET_HASH="abc#123". This was a breaking change introduced in v15 and remains in later versions. (github.com, gitlab.com)
    • Multiline values: multiline env values (useful for private keys) are supported since v15 (no special flag needed). If you rely on older single-line encodings, you can now put the multiline body inside quotes. (github.com)
    • Backtick support / quoting: v16 introduced backtick support (v16.0.0 notes) — if your values contain backticks you should quote them. (gitlab.com)
    • v16.x additions: conveniences like config.populate, accepting a URL for path option, and support for .env.vault (encrypted vault files) were added (see v16.1.0 notes). Also some packaging/browser-field fixes that affect front-end bundling (you may need polyfills when bundling for browsers). (gitlab.com)

Practical checklist for upgrading from v16 → latest (or for adopting latest now)

  • Audit your .env files for unquoted values that contain # or backticks; wrap them in quotes where needed. (This is the most common real-world breakage.)
  • If you put multiline secrets (private keys) in .env, keep them quoted or use the multiline format (supported since v15).
  • If you use dotenv in browser-bundled code, ensure polyfills for node core modules (path/os/crypto) or use a bundler plugin; dotenv is primarily intended for Node. (github.com, gitlab.com)
  • If you’re on Node 20+ and prefer the built-in option, Node provides --env-file, which may remove the need for dotenv in some setups — but many teams still use dotenv for richer features. (infisical.com)

If you want I can:

  • Check right now whether npm already publishes alchemy@0.62.2 (I can try a registry lookup or show the exact npm install command to use the GitHub release), and
  • Show exact changelog entries (links/snippets) between your current dotenv version and the latest so you can spot any other API changes specific to your code.

Citations:


Sanity-check Dependency Versions and Track Temporary Fixes

  • alchemy
    The GitHub repo has tags v0.62.0–v0.62.2, but the npm “latest” is still v0.60.2. If you need v0.62.x today, either install from GitHub (e.g.
    "alchemy": "sam-goodwin/alchemy#v0.62.1")
    or wait for v0.62.x to be published to npm. Otherwise change your spec to "^0.60.2".

  • dotenv
    Latest is v17.2.1. Since v16, note that:
    • Values containing # or backticks must be quoted.
    • Multiline values are supported in quotes.
    • New helpers (config.populate, URL paths, .env.vault) exist.
    Audit your .env files for unquoted special characters and adjust as needed.

  • nitropack
    Fine as a temporary workaround. Please convert the inline comment into a TODO with an issue link so it’s easy to find and remove later. For example:

    - // temporary workaround for alchemy + tanstack start
    + // TODO [ISSUE-1234]: temporary nitropack workaround for alchemy + tanstack start; remove once fixed upstream
      nitropack: "^2.12.4",
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
alchemy: "^0.62.1",
// temporary workaround for alchemy + tanstack start
nitropack: "^2.12.4",
dotenv: "^17.2.1",
alchemy: "^0.62.1",
// TODO [ISSUE-1234]: temporary nitropack workaround for alchemy + tanstack start; remove once fixed upstream
nitropack: "^2.12.4",
dotenv: "^17.2.1",
🤖 Prompt for AI Agents
In apps/cli/src/constants.ts around lines 130 to 134, the dependency specs and
inline comment need correction: change the alchemy version to a stable
npm-compatible spec (either pin to the published npm version "^0.60.2" or point
to the GitHub tag if you intentionally need 0.62.x, e.g.
"sam-goodwin/alchemy#v0.62.1"), audit any .env files for values containing # or
backticks and ensure they are quoted to match dotenv v17 behavior (and note
multiline support), and replace the inline "temporary workaround" comment for
nitropack with a TODO that includes an issue link so the workaround is tracked
for removal later.

} as const;

export type AvailableDependencies = keyof typeof dependencyVersionMap;

export const ADDON_COMPATIBILITY: Record<Addons, readonly Frontend[]> = {
pwa: ["tanstack-router", "react-router", "solid", "next"],
tauri: ["tanstack-router", "react-router", "nuxt", "svelte", "solid"],
tauri: ["tanstack-router", "react-router", "nuxt", "svelte", "solid", "next"],
biome: [],
husky: [],
turborepo: [],
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ import { PKG_ROOT } from "../../constants";
import type { ProjectConfig } from "../../types";
import { exitCancelled } from "../../utils/errors";
import { getPackageExecutionCommand } from "../../utils/package-runner";
import { processAndCopyFiles } from "../project-generation/template-manager";
import { processAndCopyFiles } from "../core/template-manager";

export async function setupVibeRules(config: ProjectConfig) {
const { packageManager, projectDir } = config;
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -69,8 +69,8 @@ export async function setupTauri(config: ProjectConfig) {
`--window-title=${path.basename(projectDir)}`,
`--frontend-dist=${frontendDist}`,
`--dev-url=${devUrl}`,
`--before-dev-command=\"${packageManager} run dev\"`,
`--before-build-command=\"${packageManager} run build\"`,
`--before-dev-command="${packageManager} run dev"`,
`--before-build-command="${packageManager} run build"`,
];
const tauriArgsString = tauriArgs.join(" ");

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ import type { AddInput, Addons, ProjectConfig } from "../../types";
import { validateAddonCompatibility } from "../../utils/addon-compatibility";
import { updateBtsConfig } from "../../utils/bts-config";
import { exitWithError } from "../../utils/errors";
import { setupAddons } from "../setup/addons-setup";
import { setupAddons } from "../addons/addons-setup";
import {
detectProjectConfig,
isBetterTStackProject,
Expand Down Expand Up @@ -52,6 +52,7 @@ export async function addAddonsToProject(
dbSetup: detectedConfig.dbSetup || "none",
api: detectedConfig.api || "none",
webDeploy: detectedConfig.webDeploy || "none",
serverDeploy: detectedConfig.serverDeploy || "none",
};

for (const addon of input.addons) {
Expand Down
Loading