v0.0.2-alpha.6

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

What's changed

@nextlyhq/adapter-drizzle

Patch Changes

• #28 338b668 Thanks @faisal-rx! - Fix Cannot find package '@nextlyhq/plugin-form-builder' on pnpm dev for blank scaffolds. The base admin page (templates/base/src/app/admin/[[...params]]/page.tsx) and the existing-project admin generator both hard-coded three side-effect imports for @nextlyhq/plugin-form-builder, but the package was only added to package.json on the fresh-scaffold npm path. Blank scaffolds and existing-project installs got the imports without the dep, so next dev failed at module resolution. The plugin is now opt-in per template: blank ships a plugin-less admin page; the blog template overlays a blog-specific admin page that re-adds the imports (mirroring how formBuilderPlugin is registered only in the blog config). generatePackageJson and the yalc paths in installDependencies accept a projectType and only include @nextlyhq/plugin-form-builder when the selected template uses it.

@nextlyhq/adapter-mysql

Patch Changes

• #28 338b668 Thanks @faisal-rx! - Fix Cannot find package '@nextlyhq/plugin-form-builder' on pnpm dev for blank scaffolds. The base admin page (templates/base/src/app/admin/[[...params]]/page.tsx) and the existing-project admin generator both hard-coded three side-effect imports for @nextlyhq/plugin-form-builder, but the package was only added to package.json on the fresh-scaffold npm path. Blank scaffolds and existing-project installs got the imports without the dep, so next dev failed at module resolution. The plugin is now opt-in per template: blank ships a plugin-less admin page; the blog template overlays a blog-specific admin page that re-adds the imports (mirroring how formBuilderPlugin is registered only in the blog config). generatePackageJson and the yalc paths in installDependencies accept a projectType and only include @nextlyhq/plugin-form-builder when the selected template uses it.

• Updated dependencies [338b668]:

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

@nextlyhq/adapter-postgres

Patch Changes

• #28 338b668 Thanks @faisal-rx! - Fix Cannot find package '@nextlyhq/plugin-form-builder' on pnpm dev for blank scaffolds. The base admin page (templates/base/src/app/admin/[[...params]]/page.tsx) and the existing-project admin generator both hard-coded three side-effect imports for @nextlyhq/plugin-form-builder, but the package was only added to package.json on the fresh-scaffold npm path. Blank scaffolds and existing-project installs got the imports without the dep, so next dev failed at module resolution. The plugin is now opt-in per template: blank ships a plugin-less admin page; the blog template overlays a blog-specific admin page that re-adds the imports (mirroring how formBuilderPlugin is registered only in the blog config). generatePackageJson and the yalc paths in installDependencies accept a projectType and only include @nextlyhq/plugin-form-builder when the selected template uses it.

• Updated dependencies [338b668]:

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

@nextlyhq/adapter-sqlite

Patch Changes

• #28 338b668 Thanks @faisal-rx! - Fix Cannot find package '@nextlyhq/plugin-form-builder' on pnpm dev for blank scaffolds. The base admin page (templates/base/src/app/admin/[[...params]]/page.tsx) and the existing-project admin generator both hard-coded three side-effect imports for @nextlyhq/plugin-form-builder, but the package was only added to package.json on the fresh-scaffold npm path. Blank scaffolds and existing-project installs got the imports without the dep, so next dev failed at module resolution. The plugin is now opt-in per template: blank ships a plugin-less admin page; the blog template overlays a blog-specific admin page that re-adds the imports (mirroring how formBuilderPlugin is registered only in the blog config). generatePackageJson and the yalc paths in installDependencies accept a projectType and only include @nextlyhq/plugin-form-builder when the selected template uses it.

• Updated dependencies [338b668]:

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

@nextlyhq/admin

Patch Changes

• #28 338b668 Thanks @faisal-rx! - Fix Cannot find package '@nextlyhq/plugin-form-builder' on pnpm dev for blank scaffolds. The base admin page (templates/base/src/app/admin/[[...params]]/page.tsx) and the existing-project admin generator both hard-coded three side-effect imports for @nextlyhq/plugin-form-builder, but the package was only added to package.json on the fresh-scaffold npm path. Blank scaffolds and existing-project installs got the imports without the dep, so next dev failed at module resolution. The plugin is now opt-in per template: blank ships a plugin-less admin page; the blog template overlays a blog-specific admin page that re-adds the imports (mirroring how formBuilderPlugin is registered only in the blog config). generatePackageJson and the yalc paths in installDependencies accept a projectType and only include @nextlyhq/plugin-form-builder when the selected template uses it.

• Updated dependencies [338b668]:

  • @nextlyhq/ui@0.0.2-alpha.6

create-nextly-app

Patch Changes

• #28 338b668 Thanks @faisal-rx! - Fix Cannot find package '@nextlyhq/plugin-form-builder' on pnpm dev for blank scaffolds. The base admin page (templates/base/src/app/admin/[[...params]]/page.tsx) and the existing-project admin generator both hard-coded three side-effect imports for @nextlyhq/plugin-form-builder, but the package was only added to package.json on the fresh-scaffold npm path. Blank scaffolds and existing-project installs got the imports without the dep, so next dev failed at module resolution. The plugin is now opt-in per template: blank ships a plugin-less admin page; the blog template overlays a blog-specific admin page that re-adds the imports (mirroring how formBuilderPlugin is registered only in the blog config). generatePackageJson and the yalc paths in installDependencies accept a projectType and only include @nextlyhq/plugin-form-builder when the selected template uses it.

nextly

Patch Changes

• #28 338b668 Thanks @faisal-rx! - Fix Cannot find package '@nextlyhq/plugin-form-builder' on pnpm dev for blank scaffolds. The base admin page (templates/base/src/app/admin/[[...params]]/page.tsx) and the existing-project admin generator both hard-coded three side-effect imports for @nextlyhq/plugin-form-builder, but the package was only added to package.json on the fresh-scaffold npm path. Blank scaffolds and existing-project installs got the imports without the dep, so next dev failed at module resolution. The plugin is now opt-in per template: blank ships a plugin-less admin page; the blog template overlays a blog-specific admin page that re-adds the imports (mirroring how formBuilderPlugin is registered only in the blog config). generatePackageJson and the yalc paths in installDependencies accept a projectType and only include @nextlyhq/plugin-form-builder when the selected template uses it.

• Updated dependencies [338b668]:

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

@nextlyhq/plugin-form-builder

Patch Changes

• #28 338b668 Thanks @faisal-rx! - Fix Cannot find package '@nextlyhq/plugin-form-builder' on pnpm dev for blank scaffolds. The base admin page (templates/base/src/app/admin/[[...params]]/page.tsx) and the existing-project admin generator both hard-coded three side-effect imports for @nextlyhq/plugin-form-builder, but the package was only added to package.json on the fresh-scaffold npm path. Blank scaffolds and existing-project installs got the imports without the dep, so next dev failed at module resolution. The plugin is now opt-in per template: blank ships a plugin-less admin page; the blog template overlays a blog-specific admin page that re-adds the imports (mirroring how formBuilderPlugin is registered only in the blog config). generatePackageJson and the yalc paths in installDependencies accept a projectType and only include @nextlyhq/plugin-form-builder when the selected template uses it.

• Updated dependencies [338b668]:

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

@nextlyhq/storage-s3

Patch Changes

• #28 338b668 Thanks @faisal-rx! - Fix Cannot find package '@nextlyhq/plugin-form-builder' on pnpm dev for blank scaffolds. The base admin page (templates/base/src/app/admin/[[...params]]/page.tsx) and the existing-project admin generator both hard-coded three side-effect imports for @nextlyhq/plugin-form-builder, but the package was only added to package.json on the fresh-scaffold npm path. Blank scaffolds and existing-project installs got the imports without the dep, so next dev failed at module resolution. The plugin is now opt-in per template: blank ships a plugin-less admin page; the blog template overlays a blog-specific admin page that re-adds the imports (mirroring how formBuilderPlugin is registered only in the blog config). generatePackageJson and the yalc paths in installDependencies accept a projectType and only include @nextlyhq/plugin-form-builder when the selected template uses it.

@nextlyhq/storage-uploadthing

Patch Changes

• #28 338b668 Thanks @faisal-rx! - Fix Cannot find package '@nextlyhq/plugin-form-builder' on pnpm dev for blank scaffolds. The base admin page (templates/base/src/app/admin/[[...params]]/page.tsx) and the existing-project admin generator both hard-coded three side-effect imports for @nextlyhq/plugin-form-builder, but the package was only added to package.json on the fresh-scaffold npm path. Blank scaffolds and existing-project installs got the imports without the dep, so next dev failed at module resolution. The plugin is now opt-in per template: blank ships a plugin-less admin page; the blog template overlays a blog-specific admin page that re-adds the imports (mirroring how formBuilderPlugin is registered only in the blog config). generatePackageJson and the yalc paths in installDependencies accept a projectType and only include @nextlyhq/plugin-form-builder when the selected template uses it.

@nextlyhq/storage-vercel-blob

Patch Changes

• #28 338b668 Thanks @faisal-rx! - Fix Cannot find package '@nextlyhq/plugin-form-builder' on pnpm dev for blank scaffolds. The base admin page (templates/base/src/app/admin/[[...params]]/page.tsx) and the existing-project admin generator both hard-coded three side-effect imports for @nextlyhq/plugin-form-builder, but the package was only added to package.json on the fresh-scaffold npm path. Blank scaffolds and existing-project installs got the imports without the dep, so next dev failed at module resolution. The plugin is now opt-in per template: blank ships a plugin-less admin page; the blog template overlays a blog-specific admin page that re-adds the imports (mirroring how formBuilderPlugin is registered only in the blog config). generatePackageJson and the yalc paths in installDependencies accept a projectType and only include @nextlyhq/plugin-form-builder when the selected template uses it.

@nextlyhq/ui

Patch Changes

• #28 338b668 Thanks @faisal-rx! - Fix Cannot find package '@nextlyhq/plugin-form-builder' on pnpm dev for blank scaffolds. The base admin page (templates/base/src/app/admin/[[...params]]/page.tsx) and the existing-project admin generator both hard-coded three side-effect imports for @nextlyhq/plugin-form-builder, but the package was only added to package.json on the fresh-scaffold npm path. Blank scaffolds and existing-project installs got the imports without the dep, so next dev failed at module resolution. The plugin is now opt-in per template: blank ships a plugin-less admin page; the blog template overlays a blog-specific admin page that re-adds the imports (mirroring how formBuilderPlugin is registered only in the blog config). generatePackageJson and the yalc paths in installDependencies accept a projectType and only include @nextlyhq/plugin-form-builder when the selected template uses it.