Rspack/Rsbuild: `@workflow/swc-plugin` can't run in `builtin:swc-loader`. Open to an `@workflow/rsbuild`?

未关闭
#4,447 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
rust, typescript

调研方向

Start by running the documented npm install and npx rspack build reproduction, then read the @workflow/next/loader entry point. Review packages/builders/src/vercel-build-output-api.ts and the related Nitro and Astro builder files to understand the proposed integration boundaries. Done means an agreed Rsbuild integration or thin third-party path that supports the reported build and preserves existing .vercel/output/config.json content.

由索引模型根据 Issue 内容生成。

描述

@workflow/swc-plugin fails in Rspack's builtin:swc-loader, so Rsbuild/Rspack apps have no supported way to use Workflow.

Repro
npm i -D @rspack/[email protected] @rspack/[email protected] @workflow/[email protected]
// src/index.ts
export async function add(a: number, b: number) {
  'use step';
  return a + b;
}
// rspack.config.mjs
import { createRequire } from 'node:module';
const require = createRequire(import.meta.url);

export default {
  target: 'node',
  entry: './src/index.ts',
  module: {
    rules: [{
      test: /\.ts$/,
      loader: 'builtin:swc-loader',
      options: { jsc: {
        parser: { syntax: 'typescript' },
        experimental: { plugins: [[require.resolve('@workflow/swc-plugin'), { mode: 'step' }]] },
      } },
    }],
  },
};

Run npx rspack build.

Expected: the step transform runs.
Actual: failed to invoke plugin ... Failed to deserialize program received from host. The plugin pins swc_core 49 (Cargo.toml); Rspack 2.2 embeds swc_core 79.

Versions

@rspack/core 2.2.7; @workflow/swc-plugin 4.1.3 and 5.0.0-beta.7 (still swc_core 49 on main).

Workaround

@workflow/next/loader works as a plain Rspack JS loader.

Ask

Would you take an @workflow/rsbuild package? We have one working on workflow 4.8 (JS loader, BaseBuilder subclass, dev middleware) and can contribute it. If you'd rather keep it out of tree, two changes would keep a third-party plugin thin:

  1. Export the loader from a bundler-neutral path, e.g. @workflow/builders/loader.
  2. Have VercelBuildOutputAPIBuilder merge into an existing .vercel/output/config.json instead of overwriting it (vercel-build-output-api.ts#L111-L126). Nitro and Astro each re-merge it today (nitro, astro).
主要语言
TypeScript
星标
2.5k
派生
401
平均合并
1 天 21 小时
30 天内合并 PR
201

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

vercel/workflow 的其他 Issue

查看 vercel/workflow 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。