v0.0.2-alpha.7

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

What's changed

@nextlyhq/adapter-drizzle

Patch Changes

• #32 e41725d Thanks @mobeenabdullah! - Internal refactor: consolidate the packages/nextly/src/services/auth/ shim layer. The shim was a directory of one-line export * re-exports left over from an earlier reorganisation; the canonical code already lived in packages/nextly/src/domains/auth/services/. The shim directory has been removed and 29 internal call sites have been pointed at the canonical location. A duplicate test suite of 13 files (mechanical-path-only drift, no logic divergence) has been deleted in favour of the existing copies under domains/auth/__tests__/. A new @nextly/domains/* TypeScript path alias is added to match the existing @nextly/services/* / @nextly/auth/* pattern. No public exports, runtime behaviour, or wire-format changes; this is shipped as a patch because every package version moves together in the alpha train.

• #30 bd92f1b Thanks @mobeenabdullah! - create-nextly-app now prompts for a folder name when none is given on the command line. Previously, running npx create-nextly-app with no positional argument was silently treated as "install in the current directory" and then aborted with a Directory not empty error once the user finished the template and database prompts. The CLI now asks What should your project be called? with my-nextly-app pre-filled. You can accept the default with Enter, type any folder name, or type . (or ./) to install in the current directory, matching the way the positional argument already worked. When the chosen target directory is non-empty the CLI now offers a three-option recovery prompt (cancel, remove existing files and continue, or ignore files and continue) instead of aborting outright. The remove option preserves any .git directory so existing history is kept.

  Note for scripted or CI use: the no-argument form is no longer equivalent to npx create-nextly-app .; it now opens an interactive prompt. If you were relying on the previous behavior in a non-interactive environment, pass . (or any folder name) explicitly.

@nextlyhq/adapter-mysql

Patch Changes

• #32 e41725d Thanks @mobeenabdullah! - Internal refactor: consolidate the packages/nextly/src/services/auth/ shim layer. The shim was a directory of one-line export * re-exports left over from an earlier reorganisation; the canonical code already lived in packages/nextly/src/domains/auth/services/. The shim directory has been removed and 29 internal call sites have been pointed at the canonical location. A duplicate test suite of 13 files (mechanical-path-only drift, no logic divergence) has been deleted in favour of the existing copies under domains/auth/__tests__/. A new @nextly/domains/* TypeScript path alias is added to match the existing @nextly/services/* / @nextly/auth/* pattern. No public exports, runtime behaviour, or wire-format changes; this is shipped as a patch because every package version moves together in the alpha train.

• #30 bd92f1b Thanks @mobeenabdullah! - create-nextly-app now prompts for a folder name when none is given on the command line. Previously, running npx create-nextly-app with no positional argument was silently treated as "install in the current directory" and then aborted with a Directory not empty error once the user finished the template and database prompts. The CLI now asks What should your project be called? with my-nextly-app pre-filled. You can accept the default with Enter, type any folder name, or type . (or ./) to install in the current directory, matching the way the positional argument already worked. When the chosen target directory is non-empty the CLI now offers a three-option recovery prompt (cancel, remove existing files and continue, or ignore files and continue) instead of aborting outright. The remove option preserves any .git directory so existing history is kept.

  Note for scripted or CI use: the no-argument form is no longer equivalent to npx create-nextly-app .; it now opens an interactive prompt. If you were relying on the previous behavior in a non-interactive environment, pass . (or any folder name) explicitly.

• Updated dependencies [e41725d, bd92f1b]:

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

@nextlyhq/adapter-postgres

Patch Changes

• #32 e41725d Thanks @mobeenabdullah! - Internal refactor: consolidate the packages/nextly/src/services/auth/ shim layer. The shim was a directory of one-line export * re-exports left over from an earlier reorganisation; the canonical code already lived in packages/nextly/src/domains/auth/services/. The shim directory has been removed and 29 internal call sites have been pointed at the canonical location. A duplicate test suite of 13 files (mechanical-path-only drift, no logic divergence) has been deleted in favour of the existing copies under domains/auth/__tests__/. A new @nextly/domains/* TypeScript path alias is added to match the existing @nextly/services/* / @nextly/auth/* pattern. No public exports, runtime behaviour, or wire-format changes; this is shipped as a patch because every package version moves together in the alpha train.

• #30 bd92f1b Thanks @mobeenabdullah! - create-nextly-app now prompts for a folder name when none is given on the command line. Previously, running npx create-nextly-app with no positional argument was silently treated as "install in the current directory" and then aborted with a Directory not empty error once the user finished the template and database prompts. The CLI now asks What should your project be called? with my-nextly-app pre-filled. You can accept the default with Enter, type any folder name, or type . (or ./) to install in the current directory, matching the way the positional argument already worked. When the chosen target directory is non-empty the CLI now offers a three-option recovery prompt (cancel, remove existing files and continue, or ignore files and continue) instead of aborting outright. The remove option preserves any .git directory so existing history is kept.

  Note for scripted or CI use: the no-argument form is no longer equivalent to npx create-nextly-app .; it now opens an interactive prompt. If you were relying on the previous behavior in a non-interactive environment, pass . (or any folder name) explicitly.

• Updated dependencies [e41725d, bd92f1b]:

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

@nextlyhq/adapter-sqlite

Patch Changes

• #32 e41725d Thanks @mobeenabdullah! - Internal refactor: consolidate the packages/nextly/src/services/auth/ shim layer. The shim was a directory of one-line export * re-exports left over from an earlier reorganisation; the canonical code already lived in packages/nextly/src/domains/auth/services/. The shim directory has been removed and 29 internal call sites have been pointed at the canonical location. A duplicate test suite of 13 files (mechanical-path-only drift, no logic divergence) has been deleted in favour of the existing copies under domains/auth/__tests__/. A new @nextly/domains/* TypeScript path alias is added to match the existing @nextly/services/* / @nextly/auth/* pattern. No public exports, runtime behaviour, or wire-format changes; this is shipped as a patch because every package version moves together in the alpha train.

• #30 bd92f1b Thanks @mobeenabdullah! - create-nextly-app now prompts for a folder name when none is given on the command line. Previously, running npx create-nextly-app with no positional argument was silently treated as "install in the current directory" and then aborted with a Directory not empty error once the user finished the template and database prompts. The CLI now asks What should your project be called? with my-nextly-app pre-filled. You can accept the default with Enter, type any folder name, or type . (or ./) to install in the current directory, matching the way the positional argument already worked. When the chosen target directory is non-empty the CLI now offers a three-option recovery prompt (cancel, remove existing files and continue, or ignore files and continue) instead of aborting outright. The remove option preserves any .git directory so existing history is kept.

  Note for scripted or CI use: the no-argument form is no longer equivalent to npx create-nextly-app .; it now opens an interactive prompt. If you were relying on the previous behavior in a non-interactive environment, pass . (or any folder name) explicitly.

• Updated dependencies [e41725d, bd92f1b]:

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

@nextlyhq/admin

Patch Changes

• #32 e41725d Thanks @mobeenabdullah! - Internal refactor: consolidate the packages/nextly/src/services/auth/ shim layer. The shim was a directory of one-line export * re-exports left over from an earlier reorganisation; the canonical code already lived in packages/nextly/src/domains/auth/services/. The shim directory has been removed and 29 internal call sites have been pointed at the canonical location. A duplicate test suite of 13 files (mechanical-path-only drift, no logic divergence) has been deleted in favour of the existing copies under domains/auth/__tests__/. A new @nextly/domains/* TypeScript path alias is added to match the existing @nextly/services/* / @nextly/auth/* pattern. No public exports, runtime behaviour, or wire-format changes; this is shipped as a patch because every package version moves together in the alpha train.

• #30 bd92f1b Thanks @mobeenabdullah! - create-nextly-app now prompts for a folder name when none is given on the command line. Previously, running npx create-nextly-app with no positional argument was silently treated as "install in the current directory" and then aborted with a Directory not empty error once the user finished the template and database prompts. The CLI now asks What should your project be called? with my-nextly-app pre-filled. You can accept the default with Enter, type any folder name, or type . (or ./) to install in the current directory, matching the way the positional argument already worked. When the chosen target directory is non-empty the CLI now offers a three-option recovery prompt (cancel, remove existing files and continue, or ignore files and continue) instead of aborting outright. The remove option preserves any .git directory so existing history is kept.

  Note for scripted or CI use: the no-argument form is no longer equivalent to npx create-nextly-app .; it now opens an interactive prompt. If you were relying on the previous behavior in a non-interactive environment, pass . (or any folder name) explicitly.

• Updated dependencies [e41725d, bd92f1b]:

  • @nextlyhq/ui@0.0.2-alpha.7

create-nextly-app

Patch Changes

• #32 e41725d Thanks @mobeenabdullah! - Internal refactor: consolidate the packages/nextly/src/services/auth/ shim layer. The shim was a directory of one-line export * re-exports left over from an earlier reorganisation; the canonical code already lived in packages/nextly/src/domains/auth/services/. The shim directory has been removed and 29 internal call sites have been pointed at the canonical location. A duplicate test suite of 13 files (mechanical-path-only drift, no logic divergence) has been deleted in favour of the existing copies under domains/auth/__tests__/. A new @nextly/domains/* TypeScript path alias is added to match the existing @nextly/services/* / @nextly/auth/* pattern. No public exports, runtime behaviour, or wire-format changes; this is shipped as a patch because every package version moves together in the alpha train.

• #30 bd92f1b Thanks @mobeenabdullah! - create-nextly-app now prompts for a folder name when none is given on the command line. Previously, running npx create-nextly-app with no positional argument was silently treated as "install in the current directory" and then aborted with a Directory not empty error once the user finished the template and database prompts. The CLI now asks What should your project be called? with my-nextly-app pre-filled. You can accept the default with Enter, type any folder name, or type . (or ./) to install in the current directory, matching the way the positional argument already worked. When the chosen target directory is non-empty the CLI now offers a three-option recovery prompt (cancel, remove existing files and continue, or ignore files and continue) instead of aborting outright. The remove option preserves any .git directory so existing history is kept.

  Note for scripted or CI use: the no-argument form is no longer equivalent to npx create-nextly-app .; it now opens an interactive prompt. If you were relying on the previous behavior in a non-interactive environment, pass . (or any folder name) explicitly.

nextly

Patch Changes

• #32 e41725d Thanks @mobeenabdullah! - Internal refactor: consolidate the packages/nextly/src/services/auth/ shim layer. The shim was a directory of one-line export * re-exports left over from an earlier reorganisation; the canonical code already lived in packages/nextly/src/domains/auth/services/. The shim directory has been removed and 29 internal call sites have been pointed at the canonical location. A duplicate test suite of 13 files (mechanical-path-only drift, no logic divergence) has been deleted in favour of the existing copies under domains/auth/__tests__/. A new @nextly/domains/* TypeScript path alias is added to match the existing @nextly/services/* / @nextly/auth/* pattern. No public exports, runtime behaviour, or wire-format changes; this is shipped as a patch because every package version moves together in the alpha train.

• #30 bd92f1b Thanks @mobeenabdullah! - create-nextly-app now prompts for a folder name when none is given on the command line. Previously, running npx create-nextly-app with no positional argument was silently treated as "install in the current directory" and then aborted with a Directory not empty error once the user finished the template and database prompts. The CLI now asks What should your project be called? with my-nextly-app pre-filled. You can accept the default with Enter, type any folder name, or type . (or ./) to install in the current directory, matching the way the positional argument already worked. When the chosen target directory is non-empty the CLI now offers a three-option recovery prompt (cancel, remove existing files and continue, or ignore files and continue) instead of aborting outright. The remove option preserves any .git directory so existing history is kept.

  Note for scripted or CI use: the no-argument form is no longer equivalent to npx create-nextly-app .; it now opens an interactive prompt. If you were relying on the previous behavior in a non-interactive environment, pass . (or any folder name) explicitly.

• Updated dependencies [e41725d, bd92f1b]:

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

@nextlyhq/plugin-form-builder

Patch Changes

• #32 e41725d Thanks @mobeenabdullah! - Internal refactor: consolidate the packages/nextly/src/services/auth/ shim layer. The shim was a directory of one-line export * re-exports left over from an earlier reorganisation; the canonical code already lived in packages/nextly/src/domains/auth/services/. The shim directory has been removed and 29 internal call sites have been pointed at the canonical location. A duplicate test suite of 13 files (mechanical-path-only drift, no logic divergence) has been deleted in favour of the existing copies under domains/auth/__tests__/. A new @nextly/domains/* TypeScript path alias is added to match the existing @nextly/services/* / @nextly/auth/* pattern. No public exports, runtime behaviour, or wire-format changes; this is shipped as a patch because every package version moves together in the alpha train.

• #30 bd92f1b Thanks @mobeenabdullah! - create-nextly-app now prompts for a folder name when none is given on the command line. Previously, running npx create-nextly-app with no positional argument was silently treated as "install in the current directory" and then aborted with a Directory not empty error once the user finished the template and database prompts. The CLI now asks What should your project be called? with my-nextly-app pre-filled. You can accept the default with Enter, type any folder name, or type . (or ./) to install in the current directory, matching the way the positional argument already worked. When the chosen target directory is non-empty the CLI now offers a three-option recovery prompt (cancel, remove existing files and continue, or ignore files and continue) instead of aborting outright. The remove option preserves any .git directory so existing history is kept.

  Note for scripted or CI use: the no-argument form is no longer equivalent to npx create-nextly-app .; it now opens an interactive prompt. If you were relying on the previous behavior in a non-interactive environment, pass . (or any folder name) explicitly.

• Updated dependencies [e41725d, bd92f1b]:

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

@nextlyhq/storage-s3

Patch Changes

• #32 e41725d Thanks @mobeenabdullah! - Internal refactor: consolidate the packages/nextly/src/services/auth/ shim layer. The shim was a directory of one-line export * re-exports left over from an earlier reorganisation; the canonical code already lived in packages/nextly/src/domains/auth/services/. The shim directory has been removed and 29 internal call sites have been pointed at the canonical location. A duplicate test suite of 13 files (mechanical-path-only drift, no logic divergence) has been deleted in favour of the existing copies under domains/auth/__tests__/. A new @nextly/domains/* TypeScript path alias is added to match the existing @nextly/services/* / @nextly/auth/* pattern. No public exports, runtime behaviour, or wire-format changes; this is shipped as a patch because every package version moves together in the alpha train.

• #30 bd92f1b Thanks @mobeenabdullah! - create-nextly-app now prompts for a folder name when none is given on the command line. Previously, running npx create-nextly-app with no positional argument was silently treated as "install in the current directory" and then aborted with a Directory not empty error once the user finished the template and database prompts. The CLI now asks What should your project be called? with my-nextly-app pre-filled. You can accept the default with Enter, type any folder name, or type . (or ./) to install in the current directory, matching the way the positional argument already worked. When the chosen target directory is non-empty the CLI now offers a three-option recovery prompt (cancel, remove existing files and continue, or ignore files and continue) instead of aborting outright. The remove option preserves any .git directory so existing history is kept.

  Note for scripted or CI use: the no-argument form is no longer equivalent to npx create-nextly-app .; it now opens an interactive prompt. If you were relying on the previous behavior in a non-interactive environment, pass . (or any folder name) explicitly.

@nextlyhq/storage-uploadthing

Patch Changes

• #32 e41725d Thanks @mobeenabdullah! - Internal refactor: consolidate the packages/nextly/src/services/auth/ shim layer. The shim was a directory of one-line export * re-exports left over from an earlier reorganisation; the canonical code already lived in packages/nextly/src/domains/auth/services/. The shim directory has been removed and 29 internal call sites have been pointed at the canonical location. A duplicate test suite of 13 files (mechanical-path-only drift, no logic divergence) has been deleted in favour of the existing copies under domains/auth/__tests__/. A new @nextly/domains/* TypeScript path alias is added to match the existing @nextly/services/* / @nextly/auth/* pattern. No public exports, runtime behaviour, or wire-format changes; this is shipped as a patch because every package version moves together in the alpha train.

• #30 bd92f1b Thanks @mobeenabdullah! - create-nextly-app now prompts for a folder name when none is given on the command line. Previously, running npx create-nextly-app with no positional argument was silently treated as "install in the current directory" and then aborted with a Directory not empty error once the user finished the template and database prompts. The CLI now asks What should your project be called? with my-nextly-app pre-filled. You can accept the default with Enter, type any folder name, or type . (or ./) to install in the current directory, matching the way the positional argument already worked. When the chosen target directory is non-empty the CLI now offers a three-option recovery prompt (cancel, remove existing files and continue, or ignore files and continue) instead of aborting outright. The remove option preserves any .git directory so existing history is kept.

  Note for scripted or CI use: the no-argument form is no longer equivalent to npx create-nextly-app .; it now opens an interactive prompt. If you were relying on the previous behavior in a non-interactive environment, pass . (or any folder name) explicitly.

@nextlyhq/storage-vercel-blob

Patch Changes

• #32 e41725d Thanks @mobeenabdullah! - Internal refactor: consolidate the packages/nextly/src/services/auth/ shim layer. The shim was a directory of one-line export * re-exports left over from an earlier reorganisation; the canonical code already lived in packages/nextly/src/domains/auth/services/. The shim directory has been removed and 29 internal call sites have been pointed at the canonical location. A duplicate test suite of 13 files (mechanical-path-only drift, no logic divergence) has been deleted in favour of the existing copies under domains/auth/__tests__/. A new @nextly/domains/* TypeScript path alias is added to match the existing @nextly/services/* / @nextly/auth/* pattern. No public exports, runtime behaviour, or wire-format changes; this is shipped as a patch because every package version moves together in the alpha train.

• #30 bd92f1b Thanks @mobeenabdullah! - create-nextly-app now prompts for a folder name when none is given on the command line. Previously, running npx create-nextly-app with no positional argument was silently treated as "install in the current directory" and then aborted with a Directory not empty error once the user finished the template and database prompts. The CLI now asks What should your project be called? with my-nextly-app pre-filled. You can accept the default with Enter, type any folder name, or type . (or ./) to install in the current directory, matching the way the positional argument already worked. When the chosen target directory is non-empty the CLI now offers a three-option recovery prompt (cancel, remove existing files and continue, or ignore files and continue) instead of aborting outright. The remove option preserves any .git directory so existing history is kept.

  Note for scripted or CI use: the no-argument form is no longer equivalent to npx create-nextly-app .; it now opens an interactive prompt. If you were relying on the previous behavior in a non-interactive environment, pass . (or any folder name) explicitly.

@nextlyhq/ui

Patch Changes

• #32 e41725d Thanks @mobeenabdullah! - Internal refactor: consolidate the packages/nextly/src/services/auth/ shim layer. The shim was a directory of one-line export * re-exports left over from an earlier reorganisation; the canonical code already lived in packages/nextly/src/domains/auth/services/. The shim directory has been removed and 29 internal call sites have been pointed at the canonical location. A duplicate test suite of 13 files (mechanical-path-only drift, no logic divergence) has been deleted in favour of the existing copies under domains/auth/__tests__/. A new @nextly/domains/* TypeScript path alias is added to match the existing @nextly/services/* / @nextly/auth/* pattern. No public exports, runtime behaviour, or wire-format changes; this is shipped as a patch because every package version moves together in the alpha train.

• #30 bd92f1b Thanks @mobeenabdullah! - create-nextly-app now prompts for a folder name when none is given on the command line. Previously, running npx create-nextly-app with no positional argument was silently treated as "install in the current directory" and then aborted with a Directory not empty error once the user finished the template and database prompts. The CLI now asks What should your project be called? with my-nextly-app pre-filled. You can accept the default with Enter, type any folder name, or type . (or ./) to install in the current directory, matching the way the positional argument already worked. When the chosen target directory is non-empty the CLI now offers a three-option recovery prompt (cancel, remove existing files and continue, or ignore files and continue) instead of aborting outright. The remove option preserves any .git directory so existing history is kept.

  Note for scripted or CI use: the no-argument form is no longer equivalent to npx create-nextly-app .; it now opens an interactive prompt. If you were relying on the previous behavior in a non-interactive environment, pass . (or any folder name) explicitly.