TanStack / TanStack/router

Adding @module-federation/vite breaks vanilla @tanstack start project

Open
#7,032 4 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
15.1k
Forks
1.9k
Avg merge
1d 20h
Merged PRs (30d)
143

Description

Which project does this relate to?

Start

Describe the bug

After generating a new project, adding @module-federation/vite breaks the build.

Similar to #4516

Your Example Website or App

https://github.com/jsg2021/tanstack-start-module-federation-issue

Steps to Reproduce the Bug or Issue

run build

Expected behavior

Build succeeds with normal output plus federated assets

This check probably needs to be more sophisticated: https://github.com/TanStack/router/blob/b1c0f4602df7d3950df199e6471774f0520a359b/packages/start-plugin-core/src/start-manifest-plugin/manifestBuilder.ts#L195-L200

We can produce multiple "entry" points... Is there a way to flag which one we want in this context?

Screenshots or Videos

No response

Platform
  • Router / Start Version: 1.167.6
  • OS: macOS/Linux
  • Browser: irrelevant, in terminal.
  • Bundler: Vite
  • Bundler Version: 7.3.1
Additional context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked reproduction repository and run its build command to observe how adding @module-federation/vite fails. Read packages/start-plugin-core/src/start-manifest-plugin/manifestBuilder.ts around lines 195-200, focusing on how multiple entry points are handled. Done means a generated Start project builds successfully with normal output and federated assets.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vite
Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.