v0.0.2-alpha.12

Released all 12 packages at 0.0.2-alpha.12 in lockstep (nextly, create-nextly-app, and 10 @nextlyhq/* packages).

What's changed

@nextlyhq/adapter-drizzle

Patch Changes

• #43 bbecc0d Thanks @faisal-rx! - Fresh projects scaffolded with pnpm create nextly-app no longer crash at boot under pnpm 10+. pnpm 10 blocks dependency install scripts by default, and without an allowlist better-sqlite3 never built its native binding, so SQLite scaffolds threw Could not locate the bindings file on the first admin request. sharp, esbuild, and unrs-resolver were silently blocked too, producing a slow JS image fallback, drizzle-kit slowness, and an eslint resolver warning respectively. The scaffolder now emits pnpm.onlyBuiltDependencies in the generated package.json: sharp, esbuild, and unrs-resolver always, plus better-sqlite3 when the SQLite adapter is selected. npm, yarn, and bun ignore the pnpm-namespaced field, so it is harmless under those package managers.

@nextlyhq/adapter-mysql

Patch Changes

• #43 bbecc0d Thanks @faisal-rx! - Fresh projects scaffolded with pnpm create nextly-app no longer crash at boot under pnpm 10+. pnpm 10 blocks dependency install scripts by default, and without an allowlist better-sqlite3 never built its native binding, so SQLite scaffolds threw Could not locate the bindings file on the first admin request. sharp, esbuild, and unrs-resolver were silently blocked too, producing a slow JS image fallback, drizzle-kit slowness, and an eslint resolver warning respectively. The scaffolder now emits pnpm.onlyBuiltDependencies in the generated package.json: sharp, esbuild, and unrs-resolver always, plus better-sqlite3 when the SQLite adapter is selected. npm, yarn, and bun ignore the pnpm-namespaced field, so it is harmless under those package managers.

• Updated dependencies [bbecc0d]:

  • @nextlyhq/adapter-drizzle@0.0.2-alpha.12

@nextlyhq/adapter-postgres

Patch Changes

• #43 bbecc0d Thanks @faisal-rx! - Fresh projects scaffolded with pnpm create nextly-app no longer crash at boot under pnpm 10+. pnpm 10 blocks dependency install scripts by default, and without an allowlist better-sqlite3 never built its native binding, so SQLite scaffolds threw Could not locate the bindings file on the first admin request. sharp, esbuild, and unrs-resolver were silently blocked too, producing a slow JS image fallback, drizzle-kit slowness, and an eslint resolver warning respectively. The scaffolder now emits pnpm.onlyBuiltDependencies in the generated package.json: sharp, esbuild, and unrs-resolver always, plus better-sqlite3 when the SQLite adapter is selected. npm, yarn, and bun ignore the pnpm-namespaced field, so it is harmless under those package managers.

• Updated dependencies [bbecc0d]:

  • @nextlyhq/adapter-drizzle@0.0.2-alpha.12

@nextlyhq/adapter-sqlite

Patch Changes

• #43 bbecc0d Thanks @faisal-rx! - Fresh projects scaffolded with pnpm create nextly-app no longer crash at boot under pnpm 10+. pnpm 10 blocks dependency install scripts by default, and without an allowlist better-sqlite3 never built its native binding, so SQLite scaffolds threw Could not locate the bindings file on the first admin request. sharp, esbuild, and unrs-resolver were silently blocked too, producing a slow JS image fallback, drizzle-kit slowness, and an eslint resolver warning respectively. The scaffolder now emits pnpm.onlyBuiltDependencies in the generated package.json: sharp, esbuild, and unrs-resolver always, plus better-sqlite3 when the SQLite adapter is selected. npm, yarn, and bun ignore the pnpm-namespaced field, so it is harmless under those package managers.

• Updated dependencies [bbecc0d]:

  • @nextlyhq/adapter-drizzle@0.0.2-alpha.12

@nextlyhq/admin

Patch Changes

• #43 bbecc0d Thanks @faisal-rx! - Fresh projects scaffolded with pnpm create nextly-app no longer crash at boot under pnpm 10+. pnpm 10 blocks dependency install scripts by default, and without an allowlist better-sqlite3 never built its native binding, so SQLite scaffolds threw Could not locate the bindings file on the first admin request. sharp, esbuild, and unrs-resolver were silently blocked too, producing a slow JS image fallback, drizzle-kit slowness, and an eslint resolver warning respectively. The scaffolder now emits pnpm.onlyBuiltDependencies in the generated package.json: sharp, esbuild, and unrs-resolver always, plus better-sqlite3 when the SQLite adapter is selected. npm, yarn, and bun ignore the pnpm-namespaced field, so it is harmless under those package managers.

• Updated dependencies [bbecc0d]:

  • @nextlyhq/ui@0.0.2-alpha.12

create-nextly-app

Patch Changes

• #43 bbecc0d Thanks @faisal-rx! - Fresh projects scaffolded with pnpm create nextly-app no longer crash at boot under pnpm 10+. pnpm 10 blocks dependency install scripts by default, and without an allowlist better-sqlite3 never built its native binding, so SQLite scaffolds threw Could not locate the bindings file on the first admin request. sharp, esbuild, and unrs-resolver were silently blocked too, producing a slow JS image fallback, drizzle-kit slowness, and an eslint resolver warning respectively. The scaffolder now emits pnpm.onlyBuiltDependencies in the generated package.json: sharp, esbuild, and unrs-resolver always, plus better-sqlite3 when the SQLite adapter is selected. npm, yarn, and bun ignore the pnpm-namespaced field, so it is harmless under those package managers.

nextly

Patch Changes

• #43 bbecc0d Thanks @faisal-rx! - Fresh projects scaffolded with pnpm create nextly-app no longer crash at boot under pnpm 10+. pnpm 10 blocks dependency install scripts by default, and without an allowlist better-sqlite3 never built its native binding, so SQLite scaffolds threw Could not locate the bindings file on the first admin request. sharp, esbuild, and unrs-resolver were silently blocked too, producing a slow JS image fallback, drizzle-kit slowness, and an eslint resolver warning respectively. The scaffolder now emits pnpm.onlyBuiltDependencies in the generated package.json: sharp, esbuild, and unrs-resolver always, plus better-sqlite3 when the SQLite adapter is selected. npm, yarn, and bun ignore the pnpm-namespaced field, so it is harmless under those package managers.

• Updated dependencies [bbecc0d]:

  • @nextlyhq/adapter-drizzle@0.0.2-alpha.12
  • @nextlyhq/adapter-mysql@0.0.2-alpha.12
  • @nextlyhq/adapter-postgres@0.0.2-alpha.12
  • @nextlyhq/adapter-sqlite@0.0.2-alpha.12

@nextlyhq/plugin-form-builder

Patch Changes

• #43 bbecc0d Thanks @faisal-rx! - Fresh projects scaffolded with pnpm create nextly-app no longer crash at boot under pnpm 10+. pnpm 10 blocks dependency install scripts by default, and without an allowlist better-sqlite3 never built its native binding, so SQLite scaffolds threw Could not locate the bindings file on the first admin request. sharp, esbuild, and unrs-resolver were silently blocked too, producing a slow JS image fallback, drizzle-kit slowness, and an eslint resolver warning respectively. The scaffolder now emits pnpm.onlyBuiltDependencies in the generated package.json: sharp, esbuild, and unrs-resolver always, plus better-sqlite3 when the SQLite adapter is selected. npm, yarn, and bun ignore the pnpm-namespaced field, so it is harmless under those package managers.

• Updated dependencies [bbecc0d]:

  • @nextlyhq/admin@0.0.2-alpha.12
  • nextly@0.0.2-alpha.12
  • @nextlyhq/ui@0.0.2-alpha.12

@nextlyhq/storage-s3

Patch Changes

• #43 bbecc0d Thanks @faisal-rx! - Fresh projects scaffolded with pnpm create nextly-app no longer crash at boot under pnpm 10+. pnpm 10 blocks dependency install scripts by default, and without an allowlist better-sqlite3 never built its native binding, so SQLite scaffolds threw Could not locate the bindings file on the first admin request. sharp, esbuild, and unrs-resolver were silently blocked too, producing a slow JS image fallback, drizzle-kit slowness, and an eslint resolver warning respectively. The scaffolder now emits pnpm.onlyBuiltDependencies in the generated package.json: sharp, esbuild, and unrs-resolver always, plus better-sqlite3 when the SQLite adapter is selected. npm, yarn, and bun ignore the pnpm-namespaced field, so it is harmless under those package managers.

@nextlyhq/storage-uploadthing

Patch Changes

• #43 bbecc0d Thanks @faisal-rx! - Fresh projects scaffolded with pnpm create nextly-app no longer crash at boot under pnpm 10+. pnpm 10 blocks dependency install scripts by default, and without an allowlist better-sqlite3 never built its native binding, so SQLite scaffolds threw Could not locate the bindings file on the first admin request. sharp, esbuild, and unrs-resolver were silently blocked too, producing a slow JS image fallback, drizzle-kit slowness, and an eslint resolver warning respectively. The scaffolder now emits pnpm.onlyBuiltDependencies in the generated package.json: sharp, esbuild, and unrs-resolver always, plus better-sqlite3 when the SQLite adapter is selected. npm, yarn, and bun ignore the pnpm-namespaced field, so it is harmless under those package managers.

@nextlyhq/storage-vercel-blob

Patch Changes

• #43 bbecc0d Thanks @faisal-rx! - Fresh projects scaffolded with pnpm create nextly-app no longer crash at boot under pnpm 10+. pnpm 10 blocks dependency install scripts by default, and without an allowlist better-sqlite3 never built its native binding, so SQLite scaffolds threw Could not locate the bindings file on the first admin request. sharp, esbuild, and unrs-resolver were silently blocked too, producing a slow JS image fallback, drizzle-kit slowness, and an eslint resolver warning respectively. The scaffolder now emits pnpm.onlyBuiltDependencies in the generated package.json: sharp, esbuild, and unrs-resolver always, plus better-sqlite3 when the SQLite adapter is selected. npm, yarn, and bun ignore the pnpm-namespaced field, so it is harmless under those package managers.

@nextlyhq/ui

Patch Changes

• #43 bbecc0d Thanks @faisal-rx! - Fresh projects scaffolded with pnpm create nextly-app no longer crash at boot under pnpm 10+. pnpm 10 blocks dependency install scripts by default, and without an allowlist better-sqlite3 never built its native binding, so SQLite scaffolds threw Could not locate the bindings file on the first admin request. sharp, esbuild, and unrs-resolver were silently blocked too, producing a slow JS image fallback, drizzle-kit slowness, and an eslint resolver warning respectively. The scaffolder now emits pnpm.onlyBuiltDependencies in the generated package.json: sharp, esbuild, and unrs-resolver always, plus better-sqlite3 when the SQLite adapter is selected. npm, yarn, and bun ignore the pnpm-namespaced field, so it is harmless under those package managers.