1 hours ago
shiki

v4.0.0

   🚨 Breaking Changes

   🚀 Features

3 hours ago
vite

v8.0.0-beta.16

Please refer to CHANGELOG.md for details.

5 hours ago
rspack

v2.0.0-beta.4

What's Changed

Performance Improvements ⚡

New Features 🎉

Bug Fixes 🐞

Refactor 🔨

Document Updates 📖

Other Changes

Full Changelog: https://github.com/web-infra-dev/rspack/compare/v2.0.0-beta.3...v2.0.0-beta.4

5 hours ago
next.js

v16.2.0-canary.65

Core Changes

  • Turbopack: Panic if a top-level task attempts an eventually consistent read: #89735
  • Fix middleware case with adapters: #90624

Misc Changes

  • Turbopack server HMR: inline source maps for evaled modules: #90561

Credits

Huge thanks to @bgw, @wbinnssmith, and @ijjk for helping!

6 hours ago
slidev

v52.13.0

   🚀 Features

   🐞 Bug Fixes

8 hours ago
next.js

v16.2.0-canary.64

Core Changes

  • Fix edge index page _next/data route: #90611
  • Turbopack server hmr: Implement restart event: #90550

Misc Changes

  • Pre-warm a single NodeJS instance when the next devserver starts: #90174

Credits

Huge thanks to @ijjk, @andrewimm, and @wbinnssmith for helping!

10 hours ago
swc
10 hours ago
astro

@astrojs/node@10.0.0-beta.6

Patch Changes

  • #15495 5b99e90 Thanks @leekeh! - Refactors to use middlewareMode adapter feature (set to classic)

  • #15657 cb625b6 Thanks @qzio! - Adds a new security.actionBodySizeLimit option to configure the maximum size of Astro Actions request bodies.

    This lets you increase the default 1 MB limit when your actions need to accept larger payloads. For example, actions that handle file uploads or large JSON payloads can now opt in to a higher limit.

    If you do not set this option, Astro continues to enforce the 1 MB default to help prevent abuse.

    // astro.config.mjs
    export default defineConfig({
      security: {
        actionBodySizeLimit: 10 * 1024 * 1024, // set to 10 MB
      },
    });
10 hours ago
astro

@astrojs/vercel@10.0.0-beta.6

Minor Changes

  • #15495 5b99e90 Thanks @leekeh! - Adds new middlewareMode adapter feature and deprecates edgeMiddleware option

    The edgeMiddleware option is now deprecated and will be removed in a future release, so users should transition to using the new middlewareMode feature as soon as possible.

    export default defineConfig({
      adapter: vercel({
    -    edgeMiddleware: true
    +    middlewareMode: 'edge'
      })
    })
10 hours ago
astro

astro@6.0.0-beta.17

Minor Changes

  • #15495 5b99e90 Thanks @leekeh! - Adds a new middlewareMode adapter feature to replace the previous edgeMiddleware option.

    This feature only impacts adapter authors. If your adapter supports edgeMiddleware, you should upgrade to the new middlewareMode option to specify the middleware mode for your adapter as soon as possible. The edgeMiddleware feature is deprecated and will be removed in a future major release.

    export default function createIntegration() {
      return {
        name: '@example/my-adapter',
        hooks: {
          'astro:config:done': ({ setAdapter }) => {
            setAdapter({
              name: '@example/my-adapter',
              serverEntrypoint: '@example/my-adapter/server.js',
              adapterFeatures: {
    -            edgeMiddleware: true
    +            middlewareMode: 'edge'
              }
            });
          },
        },
      };
    }

Patch Changes

  • #15657 cb625b6 Thanks @qzio! - Adds a new security.actionBodySizeLimit option to configure the maximum size of Astro Actions request bodies.

    This lets you increase the default 1 MB limit when your actions need to accept larger payloads. For example, actions that handle file uploads or large JSON payloads can now opt in to a higher limit.

    If you do not set this option, Astro continues to enforce the 1 MB default to help prevent abuse.

    // astro.config.mjs
    export default defineConfig({
      security: {
        actionBodySizeLimit: 10 * 1024 * 1024, // set to 10 MB
      },
    });
  • Updated dependencies [1fa4177]:

    • @astrojs/markdown-remark@7.0.0-beta.8