Skip to content

v0.0.2-alpha.9

Pre-release
Pre-release

Choose a tag to compare

View all tags
@mobeenabdullah mobeenabdullah released this 18 May 13:45
· 247 commits to main since this release
v0.0.2-alpha.9
2efce44
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

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

What's changed

@nextlyhq/adapter-drizzle

Patch Changes

  • #36 10479d0 Thanks @faisal-rx! - Media URLs returned from the API are now absolute. Previously, the local storage adapter wrote /uploads/... paths and surfaced them verbatim in API responses — mobile clients, edge workers, and any consumer without the deployment's origin baked in could not resolve the URL. Now, MediaService responses, populated media relations on entry responses, and the collection upload handlers (POST / GET /admin/api/collections/<slug>/uploads) prefix relative URLs with NEXT_PUBLIC_APP_URL (priority: emailConfig.baseUrl override > NEXT_PUBLIC_APP_URL > http://localhost:3000 in dev). Cloud-adapter URLs (S3, Vercel Blob, R2) are already absolute and pass through unchanged. Consumers that previously concatenated the base URL themselves should drop the prefix — double-prefix detection is in place, but the new behaviour means the prefix is no longer needed. The env schema already requires NEXT_PUBLIC_APP_URL in production, so the localhost fallback is only reachable in development.

    Internal: extracted a shared getBaseUrl(override?) helper at src/shared/lib/get-base-url.ts so the email service and the new media-absolutization path resolve through one priority chain. EmailService.getBaseUrl and the new getMediaBaseUrl both delegate to it.

@nextlyhq/adapter-mysql

Patch Changes

  • #36 10479d0 Thanks @faisal-rx! - Media URLs returned from the API are now absolute. Previously, the local storage adapter wrote /uploads/... paths and surfaced them verbatim in API responses — mobile clients, edge workers, and any consumer without the deployment's origin baked in could not resolve the URL. Now, MediaService responses, populated media relations on entry responses, and the collection upload handlers (POST / GET /admin/api/collections/<slug>/uploads) prefix relative URLs with NEXT_PUBLIC_APP_URL (priority: emailConfig.baseUrl override > NEXT_PUBLIC_APP_URL > http://localhost:3000 in dev). Cloud-adapter URLs (S3, Vercel Blob, R2) are already absolute and pass through unchanged. Consumers that previously concatenated the base URL themselves should drop the prefix — double-prefix detection is in place, but the new behaviour means the prefix is no longer needed. The env schema already requires NEXT_PUBLIC_APP_URL in production, so the localhost fallback is only reachable in development.

    Internal: extracted a shared getBaseUrl(override?) helper at src/shared/lib/get-base-url.ts so the email service and the new media-absolutization path resolve through one priority chain. EmailService.getBaseUrl and the new getMediaBaseUrl both delegate to it.

  • Updated dependencies [10479d0]:

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

@nextlyhq/adapter-postgres

Patch Changes

  • #36 10479d0 Thanks @faisal-rx! - Media URLs returned from the API are now absolute. Previously, the local storage adapter wrote /uploads/... paths and surfaced them verbatim in API responses — mobile clients, edge workers, and any consumer without the deployment's origin baked in could not resolve the URL. Now, MediaService responses, populated media relations on entry responses, and the collection upload handlers (POST / GET /admin/api/collections/<slug>/uploads) prefix relative URLs with NEXT_PUBLIC_APP_URL (priority: emailConfig.baseUrl override > NEXT_PUBLIC_APP_URL > http://localhost:3000 in dev). Cloud-adapter URLs (S3, Vercel Blob, R2) are already absolute and pass through unchanged. Consumers that previously concatenated the base URL themselves should drop the prefix — double-prefix detection is in place, but the new behaviour means the prefix is no longer needed. The env schema already requires NEXT_PUBLIC_APP_URL in production, so the localhost fallback is only reachable in development.

    Internal: extracted a shared getBaseUrl(override?) helper at src/shared/lib/get-base-url.ts so the email service and the new media-absolutization path resolve through one priority chain. EmailService.getBaseUrl and the new getMediaBaseUrl both delegate to it.

  • Updated dependencies [10479d0]:

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

@nextlyhq/adapter-sqlite

Patch Changes

  • #36 10479d0 Thanks @faisal-rx! - Media URLs returned from the API are now absolute. Previously, the local storage adapter wrote /uploads/... paths and surfaced them verbatim in API responses — mobile clients, edge workers, and any consumer without the deployment's origin baked in could not resolve the URL. Now, MediaService responses, populated media relations on entry responses, and the collection upload handlers (POST / GET /admin/api/collections/<slug>/uploads) prefix relative URLs with NEXT_PUBLIC_APP_URL (priority: emailConfig.baseUrl override > NEXT_PUBLIC_APP_URL > http://localhost:3000 in dev). Cloud-adapter URLs (S3, Vercel Blob, R2) are already absolute and pass through unchanged. Consumers that previously concatenated the base URL themselves should drop the prefix — double-prefix detection is in place, but the new behaviour means the prefix is no longer needed. The env schema already requires NEXT_PUBLIC_APP_URL in production, so the localhost fallback is only reachable in development.

    Internal: extracted a shared getBaseUrl(override?) helper at src/shared/lib/get-base-url.ts so the email service and the new media-absolutization path resolve through one priority chain. EmailService.getBaseUrl and the new getMediaBaseUrl both delegate to it.

  • Updated dependencies [10479d0]:

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

@nextlyhq/admin

Patch Changes

  • #36 10479d0 Thanks @faisal-rx! - Media URLs returned from the API are now absolute. Previously, the local storage adapter wrote /uploads/... paths and surfaced them verbatim in API responses — mobile clients, edge workers, and any consumer without the deployment's origin baked in could not resolve the URL. Now, MediaService responses, populated media relations on entry responses, and the collection upload handlers (POST / GET /admin/api/collections/<slug>/uploads) prefix relative URLs with NEXT_PUBLIC_APP_URL (priority: emailConfig.baseUrl override > NEXT_PUBLIC_APP_URL > http://localhost:3000 in dev). Cloud-adapter URLs (S3, Vercel Blob, R2) are already absolute and pass through unchanged. Consumers that previously concatenated the base URL themselves should drop the prefix — double-prefix detection is in place, but the new behaviour means the prefix is no longer needed. The env schema already requires NEXT_PUBLIC_APP_URL in production, so the localhost fallback is only reachable in development.

    Internal: extracted a shared getBaseUrl(override?) helper at src/shared/lib/get-base-url.ts so the email service and the new media-absolutization path resolve through one priority chain. EmailService.getBaseUrl and the new getMediaBaseUrl both delegate to it.

  • Updated dependencies [10479d0]:

    • @nextlyhq/ui@0.0.2-alpha.9

create-nextly-app

Patch Changes

  • #36 10479d0 Thanks @faisal-rx! - Media URLs returned from the API are now absolute. Previously, the local storage adapter wrote /uploads/... paths and surfaced them verbatim in API responses — mobile clients, edge workers, and any consumer without the deployment's origin baked in could not resolve the URL. Now, MediaService responses, populated media relations on entry responses, and the collection upload handlers (POST / GET /admin/api/collections/<slug>/uploads) prefix relative URLs with NEXT_PUBLIC_APP_URL (priority: emailConfig.baseUrl override > NEXT_PUBLIC_APP_URL > http://localhost:3000 in dev). Cloud-adapter URLs (S3, Vercel Blob, R2) are already absolute and pass through unchanged. Consumers that previously concatenated the base URL themselves should drop the prefix — double-prefix detection is in place, but the new behaviour means the prefix is no longer needed. The env schema already requires NEXT_PUBLIC_APP_URL in production, so the localhost fallback is only reachable in development.

    Internal: extracted a shared getBaseUrl(override?) helper at src/shared/lib/get-base-url.ts so the email service and the new media-absolutization path resolve through one priority chain. EmailService.getBaseUrl and the new getMediaBaseUrl both delegate to it.

nextly

Patch Changes

  • #36 10479d0 Thanks @faisal-rx! - Media URLs returned from the API are now absolute. Previously, the local storage adapter wrote /uploads/... paths and surfaced them verbatim in API responses — mobile clients, edge workers, and any consumer without the deployment's origin baked in could not resolve the URL. Now, MediaService responses, populated media relations on entry responses, and the collection upload handlers (POST / GET /admin/api/collections/<slug>/uploads) prefix relative URLs with NEXT_PUBLIC_APP_URL (priority: emailConfig.baseUrl override > NEXT_PUBLIC_APP_URL > http://localhost:3000 in dev). Cloud-adapter URLs (S3, Vercel Blob, R2) are already absolute and pass through unchanged. Consumers that previously concatenated the base URL themselves should drop the prefix — double-prefix detection is in place, but the new behaviour means the prefix is no longer needed. The env schema already requires NEXT_PUBLIC_APP_URL in production, so the localhost fallback is only reachable in development.

    Internal: extracted a shared getBaseUrl(override?) helper at src/shared/lib/get-base-url.ts so the email service and the new media-absolutization path resolve through one priority chain. EmailService.getBaseUrl and the new getMediaBaseUrl both delegate to it.

  • Updated dependencies [10479d0]:

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

@nextlyhq/plugin-form-builder

Patch Changes

  • #36 10479d0 Thanks @faisal-rx! - Media URLs returned from the API are now absolute. Previously, the local storage adapter wrote /uploads/... paths and surfaced them verbatim in API responses — mobile clients, edge workers, and any consumer without the deployment's origin baked in could not resolve the URL. Now, MediaService responses, populated media relations on entry responses, and the collection upload handlers (POST / GET /admin/api/collections/<slug>/uploads) prefix relative URLs with NEXT_PUBLIC_APP_URL (priority: emailConfig.baseUrl override > NEXT_PUBLIC_APP_URL > http://localhost:3000 in dev). Cloud-adapter URLs (S3, Vercel Blob, R2) are already absolute and pass through unchanged. Consumers that previously concatenated the base URL themselves should drop the prefix — double-prefix detection is in place, but the new behaviour means the prefix is no longer needed. The env schema already requires NEXT_PUBLIC_APP_URL in production, so the localhost fallback is only reachable in development.

    Internal: extracted a shared getBaseUrl(override?) helper at src/shared/lib/get-base-url.ts so the email service and the new media-absolutization path resolve through one priority chain. EmailService.getBaseUrl and the new getMediaBaseUrl both delegate to it.

  • Updated dependencies [10479d0]:

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

@nextlyhq/storage-s3

Patch Changes

  • #36 10479d0 Thanks @faisal-rx! - Media URLs returned from the API are now absolute. Previously, the local storage adapter wrote /uploads/... paths and surfaced them verbatim in API responses — mobile clients, edge workers, and any consumer without the deployment's origin baked in could not resolve the URL. Now, MediaService responses, populated media relations on entry responses, and the collection upload handlers (POST / GET /admin/api/collections/<slug>/uploads) prefix relative URLs with NEXT_PUBLIC_APP_URL (priority: emailConfig.baseUrl override > NEXT_PUBLIC_APP_URL > http://localhost:3000 in dev). Cloud-adapter URLs (S3, Vercel Blob, R2) are already absolute and pass through unchanged. Consumers that previously concatenated the base URL themselves should drop the prefix — double-prefix detection is in place, but the new behaviour means the prefix is no longer needed. The env schema already requires NEXT_PUBLIC_APP_URL in production, so the localhost fallback is only reachable in development.

    Internal: extracted a shared getBaseUrl(override?) helper at src/shared/lib/get-base-url.ts so the email service and the new media-absolutization path resolve through one priority chain. EmailService.getBaseUrl and the new getMediaBaseUrl both delegate to it.

@nextlyhq/storage-uploadthing

Patch Changes

  • #36 10479d0 Thanks @faisal-rx! - Media URLs returned from the API are now absolute. Previously, the local storage adapter wrote /uploads/... paths and surfaced them verbatim in API responses — mobile clients, edge workers, and any consumer without the deployment's origin baked in could not resolve the URL. Now, MediaService responses, populated media relations on entry responses, and the collection upload handlers (POST / GET /admin/api/collections/<slug>/uploads) prefix relative URLs with NEXT_PUBLIC_APP_URL (priority: emailConfig.baseUrl override > NEXT_PUBLIC_APP_URL > http://localhost:3000 in dev). Cloud-adapter URLs (S3, Vercel Blob, R2) are already absolute and pass through unchanged. Consumers that previously concatenated the base URL themselves should drop the prefix — double-prefix detection is in place, but the new behaviour means the prefix is no longer needed. The env schema already requires NEXT_PUBLIC_APP_URL in production, so the localhost fallback is only reachable in development.

    Internal: extracted a shared getBaseUrl(override?) helper at src/shared/lib/get-base-url.ts so the email service and the new media-absolutization path resolve through one priority chain. EmailService.getBaseUrl and the new getMediaBaseUrl both delegate to it.

@nextlyhq/storage-vercel-blob

Patch Changes

  • #36 10479d0 Thanks @faisal-rx! - Media URLs returned from the API are now absolute. Previously, the local storage adapter wrote /uploads/... paths and surfaced them verbatim in API responses — mobile clients, edge workers, and any consumer without the deployment's origin baked in could not resolve the URL. Now, MediaService responses, populated media relations on entry responses, and the collection upload handlers (POST / GET /admin/api/collections/<slug>/uploads) prefix relative URLs with NEXT_PUBLIC_APP_URL (priority: emailConfig.baseUrl override > NEXT_PUBLIC_APP_URL > http://localhost:3000 in dev). Cloud-adapter URLs (S3, Vercel Blob, R2) are already absolute and pass through unchanged. Consumers that previously concatenated the base URL themselves should drop the prefix — double-prefix detection is in place, but the new behaviour means the prefix is no longer needed. The env schema already requires NEXT_PUBLIC_APP_URL in production, so the localhost fallback is only reachable in development.

    Internal: extracted a shared getBaseUrl(override?) helper at src/shared/lib/get-base-url.ts so the email service and the new media-absolutization path resolve through one priority chain. EmailService.getBaseUrl and the new getMediaBaseUrl both delegate to it.

@nextlyhq/ui

Patch Changes

  • #36 10479d0 Thanks @faisal-rx! - Media URLs returned from the API are now absolute. Previously, the local storage adapter wrote /uploads/... paths and surfaced them verbatim in API responses — mobile clients, edge workers, and any consumer without the deployment's origin baked in could not resolve the URL. Now, MediaService responses, populated media relations on entry responses, and the collection upload handlers (POST / GET /admin/api/collections/<slug>/uploads) prefix relative URLs with NEXT_PUBLIC_APP_URL (priority: emailConfig.baseUrl override > NEXT_PUBLIC_APP_URL > http://localhost:3000 in dev). Cloud-adapter URLs (S3, Vercel Blob, R2) are already absolute and pass through unchanged. Consumers that previously concatenated the base URL themselves should drop the prefix — double-prefix detection is in place, but the new behaviour means the prefix is no longer needed. The env schema already requires NEXT_PUBLIC_APP_URL in production, so the localhost fallback is only reachable in development.

    Internal: extracted a shared getBaseUrl(override?) helper at src/shared/lib/get-base-url.ts so the email service and the new media-absolutization path resolve through one priority chain. EmailService.getBaseUrl and the new getMediaBaseUrl both delegate to it.

Assets 2
Loading