v2.1.1

🐞 Patches

• 9a0ba87: fix: make sure blitz superjson custom error registers in rpc handler

v2.1.0

Releases

Minor Changes

• 3b10b13: feat: add blitz auth support for the Web Request API standard

  Usage using the new withBlitzAuth adapter in the App Router:

  import {withBlitzAuth} from "app/blitz-server"
  
  export const {POST} = withBlitzAuth({
    POST: async (_request, _params, ctx) => {
      const session = ctx.session
      await session.$revoke()
  
      return new Response(
        JSON.stringify({
          userId: session.userId,
        }),
        {status: 200},
      )
    },
  })

  feat: New Blitz RPC handler meant to with the next.js app router route.ts files

  Usage using the new rpcAppHandler function

  // app/api/rpc/[[...blitz]]/route.ts
  import {rpcAppHandler} from "@blitzjs/rpc"
  import {withBlitzAuth} from "app/blitz-server"
  
  // Usage with blitz auth
  export const {GET, POST, HEAD} = withBlitzAuth(rpcAppHandler())
  
  // Standalone usage
  export const {GET, POST, HEAD} = rpcAppHandler()

  chore: Update the app directory starter

Patch Changes

• d53da39: Improved parsing of default export names to handle higher-order components (HOCs) in the parseDefaultExportName function.

v2.0.10

🔒 Security

• 318e974: support latest v4 next-auth release that solves GHSA-7r7x-4c4q-c4qf and GHSA-v64w-49xw-qq89

⚠️ Upgrade to next-auth > v4.25.1 to use the adapter from this release

v2.0.9

🐞 Patches

• 5a14306: fix export of enhancePrisma in client bundle

v2.0.8

🐞 Patches

• 5e61a16: bug: merge existing and custom blitz turbo configs
• 7755546: fix: add missing host while initialising the next-auth adapter

v2.0.7

🐞 Patches

• ee7bf87: Turbopack support for Blitz

  This PR includes the changes required to make the Blitz loaders work with Turbopack.

  ⚠️ Upgrade to latest next canary to use this feature: >14.2.0-canary.25.
  ℹ️ While using turbopack currently few invalid config warnings will be shown, which can be ignored and should be fixed upstream in next.js. For more context: #4314

  Usage:

  pnpm blitz dev --turbo

• 178c152: fix: patch next.js to hide intentional throws of DYNAMIC_SERVER_USAGE

v2.0.6

🐞 Patches

• 76a2544: Use SIGINT signal instead of SIGABRT to stop the process, when using custom server for better compatibility with operative systems
• 5a587a6: Fix bundling issue that occurs in vercel due to the way imports were handled internally

v2.0.5

🐞 Patches

• 6f54841: fix: getBlitzContext() can only be used in React Server Components in Nextjs 13 or higher
• 8a41753: fix: remove restriction to use secure cookies in localhost / during development following spec in developer.mozilla.org/en-US/docs/Web/HTTP/Cookies#restrict_access_to_cookies

v2.0.4

🐞 Patches

• dd604c7: perf: add filter to select only non expired sessions
• 28a7904: fix: export BlitzServerMiddleware from blitz-next with next-js specific type
• f25aac0: fix: add support to codemod upgrade-legacy for projects that have their pages folder nested in a src/ folder
• 71b9950: fix: ajv dependency was not installed with blitz new

v2.0.3

🐞 Patches

• 2f5c8a3: fix: missing sodium native prebuilds required to use secure-password during server rendering
• 956a739: fix: codemod now uses the correct paths corresponding to the changes to new templates
• 47722e0: fix: search inside any subdirectory to inside src|app directories to find blitz-server.ts to use the BlitzCliConfig configurations.
• 595f400: fix: add missing prettier, pretty-quick and other missing dev dependencies in the new app template