56 minutes ago
astro

astro@5.16.9

Patch Changes

  • #15174 37ab65a Thanks @florian-lefebvre! - Adds Google Icons to built-in font providers

    To start using it, access it on fontProviders:

    import { defineConfig, fontProviders } from 'astro/config';
    
    export default defineConfig({
      experimental: {
        fonts: [
          {
            name: 'Material Symbols Outlined',
            provider: fontProviders.googleicons(),
            cssVariable: '--font-material',
          },
        ],
      },
    });
  • #15150 a77c4f4 Thanks @matthewp! - Fixes hydration for framework components inside MDX when using Astro.slots.render()

    Previously, when multiple framework components with client:* directives were passed as named slots to an Astro component in MDX, only the first slot would hydrate correctly. Subsequent slots would render their HTML but fail to include the necessary hydration scripts.

  • #15130 9b726c4 Thanks @florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API only

    Changes how font providers are implemented with updates to the FontProvider type

    This is an implementation detail that changes how font providers are created. This process allows Astro to take more control rather than relying directly on unifont types. All of Astro's built-in font providers have been updated to reflect this new type, and can be configured as before. However, using third-party unifont providers that rely on unifont types will require an update to your project code.

    Previously, an Astro FontProvider was made of a config and a runtime part. It relied directly on unifont types, which allowed a simple configuration for third-party unifont providers, but also coupled Astro's implementation to unifont, which was limiting.

    Astro's font provider implementation is now only made of a config part with dedicated hooks. This allows for the separation of config and runtime, but requires you to create a font provider object in order to use custom font providers (e.g. third-party unifont providers, or private font registeries).

    What should I do?

    If you were using a 3rd-party unifont font provider, you will now need to write an Astro FontProvider using it under the hood. For example:

    // astro.config.ts
    import { defineConfig } from "astro/config";
    import { acmeProvider, type AcmeOptions } from '@acme/unifont-provider'
    +import type { FontProvider } from "astro";
    +import type { InitializedProvider } from 'unifont';
    
    +function acme(config?: AcmeOptions): FontProvider {
    +	const provider = acmeProvider(config);
    +	let initializedProvider: InitializedProvider | undefined;
    +	return {
    +		name: provider._name,
    +		config,
    +		async init(context) {
    +			initializedProvider = await provider(context);
    +		},
    +		async resolveFont({ familyName, ...rest }) {
    +			return await initializedProvider?.resolveFont(familyName, rest);
    +		},
    +		async listFonts() {
    +			return await initializedProvider?.listFonts?.();
    +		},
    +	};
    +}
    
    export default defineConfig({
        experimental: {
            fonts: [{
    -            provider: acmeProvider({ /* ... */ }),
    +            provider: acme({ /* ... */ }),
                name: "Material Symbols Outlined",
                cssVariable: "--font-material"
            }]
        }
    });
  • #15147 9cd5b87 Thanks @matthewp! - Fixes scripts in components not rendering when a sibling <Fragment slot="..."> exists but is unused

1 hours ago
next.js

v16.1.1-canary.22

Core Changes

  • Track search string as part of "refresh state": #87203
  • Pass RouteTree into navigation function: #87256
  • Read from segment cache unknown routes: #87293
  • Pass loading boundary as part of RSC data: #87825
  • Revert "refactor: consolidate PPR into cacheComponents architecture (#88243)": #88421
  • fix: support TypeScript noUncheckedSideEffectImports for CSS imports: #88199

Misc Changes

  • docs: fix CSP example to only include unsafe-eval in development: #88407
  • docs: add PR description guidance to AGENTS.md: #88408
  • ci: Fix retry comments in workflow files: #88412
  • [test] Deflake test/integration/invalid-custom-routes/test/index.test.ts: #88416
  • [test] Remove rogue debug log: #88423

Credits

Huge thanks to @acdlite, @timneutkens, @unstubbable, @eps1lon, @wyattjoh, and @Rani367 for helping!

1 hours ago
engine

v2.15.0

New Features

Fixes

Examples

New Contributors

Full Changelog: https://github.com/playcanvas/engine/compare/v2.14.4...v2.15.0

6 hours ago
LogicFlow

@logicflow/extension@2.1.10

What's Changed

  • fix: 修复内部系统与issue反馈的问题 by @DymoneLewis in https://github.com/didi/LogicFlow/pull/2361
    • fix(extension): 修复圆角折线插件会出现没有圆角或圆角旁多了一条线的问题
    • fix(extension): 修复导出插件safetyMargin和safetyFactor导致的快照导出后不居中对齐问题 & 修改safetyFactor为1 safetyMargin为0
6 hours ago
LogicFlow

@logicflow/vue-node-registry@1.1.9

What's Changed

  • fix: 修复内部系统与issue反馈的问题 by @DymoneLewis in https://github.com/didi/LogicFlow/pull/2361
    • fix(vue-node-registry): 修复拖拽创建vue-node-registry节点时控制台报错问题
    • fix: 删除多余console.log
6 hours ago
LogicFlow

@logicflow/core@2.1.8

What's Changed

8 hours ago
zustand

v5.0.10

This version includes a fix to the persist middleware for an edge case.

What's Changed

New Contributors

Full Changelog: https://github.com/pmndrs/zustand/compare/v5.0.9...v5.0.10

10 hours ago
electron

electron v40.0.0-beta.7

Note: This is a beta release. Please file new issues for any bugs you find in it.

This release is published to npm under the beta tag and can be installed via npm install electron@beta, or npm install electron@40.0.0-beta.7.

Release Notes for v40.0.0-beta.7

Fixes

  • Fixed an issue where no cookie encryption provider was passed into the network service when cookie encryption was enabled. #49350
11 hours ago
maptalks.js

maptalks-gl@0.119.0 maptalks@1.8.0 Released

Features

  • GeoJSONVectorTileLayer 会忽略数据范围之外的瓦片请求 #2751
  • map上增加 addGroundExtent 方法, #2767
  • transcoders包增加解码方法的导出

Fixes

  • vt图层的gltf-lit插件会根据markerOpacity或markerFill中透明度,设置模型的alphaMode
  • 解决图层没有正常调用 resizeCanvas 的问题, #2770
  • 解决PointLayer下marker.setProperties没有及时渲染的问题 #2771
  • 解决vt图层打开debug后,图层mask没有正常裁剪的问题 maptalks/issues#917
  • 解决drawTool中重复绘制的问题, #2769
  • 解决vt中查询数据返回不足的问题 #2764
  • 解决创建transform-control没有指定对象时的报错 #2773

Contributors

@fuzhenn @ydfzgyj @deyihu @liubgithub


Features

  • GeoJSONVectorTileLayer will ignore tile requests beyond the data extent #2751
  • Added the addGroundExtent method to the map, #2767
  • Added export of decoding methods to the transcoders package

Fixes

  • The vt layer's gltf-lit plugin will set the model's alphaMode based on the transparency in markerOpacity or markerFill
  • Fixed the issue where the layer did not properly call resizeCanvas, #2770
  • Fixed the issue where marker.setProperties in PointLayer did not render promptly, #2771
  • Fixed the issue where the layer mask did not properly clip when debug mode was enabled in the vt layer, maptalks/issues#917
  • Fixed the issue of repeated drawing in drawTool, #2769
  • Fixed the issue of insufficient data returned in vt queries, #2764
  • Fixed the error when creating transform-control without specifying an object, #2773

Contributors

@fuzhenn @ydfzgyj @deyihu @liubgithub

12 hours ago
vue-next

v3.6.0-beta.3

For stable releases, please refer to CHANGELOG.md for details. For pre-releases, please refer to CHANGELOG.md of the minor branch.