Preview fails when next.js runs in dev mode

[espen42]

Dev mode (next dev) has special custom functionality, driven by webpack, that fails to run through the XP proxies.

Unhandled Runtime Error
ChunkLoadError: Loading chunk node_modules_next_dist_client_dev_noop_js failed.
(error: http://localhost:8080/_next/static/chunks/node_modules_next_dist_client_dev_noop_js.js)

and

Unhandled Runtime Error
TypeError: Cannot read properties of undefined (reading 'includes')

Failing assets in network tab:

node_modules_next_dist_client_dev_noop_js.js | 404 | script | webpack.js?ts=1631710165984:263 | 115 B | 106 ms
-- | -- | -- | -- | -- | --
webpack-hmr?page=%2F_draft%2F%5B%5B...contentPath%5D%5D | 404 | eventsource | persons | 159 B | 3 ms
_devPagesManifest.json | 404 | fetch | page-loader.js?ce6b:34 | 159 B | 2 ms
image?url=%2F_next%2Fstatic%2Fimage%2Fsrc%2Fpublic…ld.074583348b1b4aee2574f3e054e22a93.svg&w=96&q=75 | 404 | json | react-dom.development.js?61bb:683 | 44 B | 7 ms
__nextjs_original-stack-frame?isServerSide=false&f…require__.f.j&arguments=&lineNumber=735&column=29 | 404 | fetch | stack-frame.js?c06d:61 | 159 B | 6 ms

[espen42]

Path resolution, or hydration-update problem after the SSR? Might be related to #61 .

[espen42]

After adding /api/ to the processing in previewProxy, and the same processing in assetProxy, this appears to work.

[espen42]

Handled in new approach.