When running multiple instances of Next.js next-network may get confused as to which one is the one we're monitoring right now. Besides the port conflict (see #1) even if only one is running with the plugin, the network devtool panel will still show up for both of them. The panel should display network requests for the browser page it's on at the moment.
When running multiple instances of Next.js next-network may get confused as to which one is the one we're monitoring right now. Besides the port conflict (see #1) even if only one is running with the plugin, the network devtool panel will still show up for both of them. The panel should display network requests for the browser page it's on at the moment.