Nextjs native module different behavior in prod mode about webpack-asset-relocator-loader HOT 6 CLOSED

It might be a bug.

However, Next.js has its own asset relocation, so its probably best to use that instead.

module.exports = {
  output: 'standalone',
}

https://nextjs.org/docs/advanced-features/output-file-tracing#automatically-copying-traced-files

from webpack-asset-relocator-loader.

Thanks for the suggestion, I tried that with node-loader too.
Thing is webpack-asset-relocator-loader works great for .node on nextjs.
It's just that one problem with production mode.

from webpack-asset-relocator-loader.

Are there cases where output standalone doesn’t include the .node files?

from webpack-asset-relocator-loader.

If I setup to standalone, the module is included in production and
e.g. located in ./.next/standalone/.next/server/chunks/[hash].node,
but api route requests it from /.next/server/pages/api/[hash].node.

Should it be in ./.next/standalone/node_modules? Because it's not included there.

I have to use either node-loader or webpack-asset-relocator-loader for .node, otherwise
I get a Module parse failed: Unexpected character. The native module is compiled using neon bindings.

I've tried multiple combinations to get this to work,
the only one that works for me is the mentioned workaround at the beginning of the issue.

I'm beginning to think this issue is out of scope for this repo,
should I rather report to https://github.com/vercel/next.js?
Thanks for your help!

from webpack-asset-relocator-loader.

Yes please create an issue in the Next.js repo with the steps to reproduce.

This repo is mostly stagnant now that Next.js has its own asset handling.

from webpack-asset-relocator-loader.

I'm closing this issue. It's not a bug with Next.js or a webpack-asset-relocator-loader. I managed to solve it using my own custom loader. Problem was in how webpack_require path was set, and loader needed to return a raw binary data instead of text.
Thanks again for your help!

from webpack-asset-relocator-loader.