Module replacement using <file>@custom module pattern has no effect. You can see this if you open the "kitchensink > composition" example in this repo.
In this image we are in the "@replace" example, where the default module should have been replaced. It hasn't, as you can see by the title here.
This is still the case as of the most recent release ^3.0.0-next.186
Reproduction
git clone git@github.com:roxiness/routify.git
cd routify
npm install
cd examples/kitchensink
npm run dev
Navigate to http://127.0.0.1:1337/composition/replace
Describe the bug
Module replacement using
<file>@custom
module pattern has no effect. You can see this if you open the "kitchensink > composition" example in this repo.In this image we are in the "@replace" example, where the default module should have been replaced. It hasn't, as you can see by the title here.
This is still the case as of the most recent release
^3.0.0-next.186
Reproduction
Navigate to
http://127.0.0.1:1337/composition/replace
Logs
System Info
I've added some failing E2E tests here: https://github.com/roxiness/routify/pull/531