Zack Jackson comments

Results 996 comments of


                                            Zack Jackson

Next.js 15 Pages Router: useRouter Breaks When Declaring the Plugin

Also note: When you expose or share your own packages, if they depend on react - this causes additional issues. Because your shared module is not specifying a layer, it...

Next.js 15 Pages Router: useRouter Breaks When Declaring the Plugin

TLDR: use follow this implementation or use the version in this repo to test it out. https://github.com/ScriptedAlchemy/next-apps-ejected Ill make edits and install new canary into it to test out v15...

Next.js 15 Pages Router: useRouter Breaks When Declaring the Plugin

> @ScriptedAlchemy > > thanks for all the hard work! We managed to apply this in our project and it seems to work with the latest NextJS and React versions...

Next.js 15 Pages Router: useRouter Breaks When Declaring the Plugin

> @ScriptedAlchemy Hi > when can we expect to have a stable version for this issue. Canary version seems to be working but getting few css issues. > Please try...

[enhanced] `tapable` is not a direct dependency

can you install tappable on your end? does that resolve it?

[enhanced] `tapable` is not a direct dependency

There's a pr open. I'll merge it

chore(utils): add react 19 to peer dependencies

the utilities package is dead, you should not be using it at all. You should be using module-federation/runtime

chore(utils): add react 19 to peer dependencies

Yes please. I don't believe anything should be using that anymore.

Reconciling npm aliases and shared dependencies.

Thats because they have different share keys. you can try setting shareKey yourself ```ts /* * This file was automatically generated. * DO NOT MODIFY BY HAND. * Run `yarn...

Reconciling npm aliases and shared dependencies.

Yes that's correct! Happy it helped. I'll update my doc site to include all the types