rstackjs / rstackjs/rstack-examples
module-federation-interop does not run
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 168
- Forks
- 47
- Avg merge
- 3h 45m
- Merged PRs (30d)
- 11
Description
The webpack-mf project inside module-federation-interop on the main branch does not run.
Here is the error:
PS C:\...\rspack-examples\rspack\module-federation-interop\webpack-mf> pnpm dev
> example-module-federation-interop-webpack-mf@1.0.0 dev C:\...\rspack-examples\rspack\module-federation-interop\webpack-mf
> webpack serve
[webpack-cli] Invalid options object. Dev Server has been initialized using an options object that does not match the API schema.
- options has an unknown property '_assetEmittingPreviousFiles'. These properties are valid:
object { allowedHosts?, bonjour?, client?, compress?, devMiddleware?, headers?, historyApiFallback?, host?, hot?, ipc?, liveReload?, onListening?, open?, port?, proxy?, server?, setupExitSignals?, setupMiddlewares?, static?, watchFiles?, webSocketServer? }
ELIFECYCLE Command failed with exit code 2.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in module-federation-interop/webpack-mf and run pnpm dev to reproduce the webpack dev-server schema error. Inspect the project's dependency versions and configuration; done means the example starts without the Invalid options object error.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100