Nitro Build breaking on a require without the '.js' extension

[jcalfee]

I'm running nuxi build from Nuxt 3 where a fatal error stops the build:

ℹ Building Nitro Server (preset: node-server)                                                                                                                                                                                                                     nitro 2:54:56 PM

 ERROR  Error: Could not load raw:../../assets/graphiql.html: ENOENT: no such file or directory, open '../../assets/graphiql.html'                                                                                                                                 nitro 2:55:09 PM

This works under nuxi dev. I can see in the project I am importing, it has this file graphiql.html with a .js extension graphiql.html.js:

$ ls -l ../node_modules/.pnpm/postgraphile@4.13.0/node_modules/postgraphile/build/assets
total 2076
-rw-r--r-- 11 james james      95 Jan  6  2023 favicon.ico.d.ts
-rw-r--r-- 11 james james   20702 Jan  6  2023 favicon.ico.js
-rw-r--r-- 11 james james 1045736 Jan  6  2023 graphiql.html.d.ts
-rw-r--r-- 11 james james 1046195 Jan  6  2023 graphiql.html.js

And tries to import it using require and probably relying on require to search for "js" const graphiql_html_1 = require("../../assets/graphiql.html"). This is not my package. Does Nitro have a way to get node to search, looking for the js extension?

Thank you

[jcalfee]

Looks like the node devs have been getting a lot of slack over this for some time now: nodejs/node#30927

One comment points to --experimental-specifier-resolution, but I don't see that in node v16's help but it does work:

$ >test.js
$ node --experimental-specifier-resolution=node
(node:480844) ExperimentalWarning: The Node.js specifier resolution flag is experimental. It could change or be removed at any time.
(Use `node --trace-warnings ...` to show where the warning was created)
Welcome to Node.js v16.17.1.
Type ".help" for more information.
> await import('./test')
[Module: null prototype] {  }

I'm not confident it will not be removed as stated in the warning, but it works and may be an option. Now, does nuxi build allow for a node parameter? I do not see this in the cli help and the runtimeconfig seams to be missing parameters like esbuild and something like node: {args} ...

[jcalfee]

It would probably be a custom loader instead of that flag: nodejs/node#30927 (comment)

[Hebilicious]

You can pass node options like this NODE_OPTIONS=--experimental-specifier-resolution=node nuxi build (or use environment variables).
For the custom loader, you probably gonna need a custom build script.
For the esbuild options you can pass them in your nitro config https://github.com/unjs/nitro/blob/6bc50b2f9416dc9af6ba327440deea2ec8e35a33/src/types/nitro.ts#L262

[jcalfee]

I see that NODE_OPTIONS is picked up because node prints its warning just before "Building client...", however, after the "Client Build in Xms" message it goes on to "Building server...", does not print the warning from "node" and the build fails in the import above that is without the ".js" extension. Is it a separate invocation of "node" and is the NODE_OPTIONS somehow not passed down? Should there be a place for client and server node options?

[jcalfee]

I tried export NODE_OPTIONS=...., who knows. That did not seam to make it down to the server.

[Hebilicious]

@jcalfee If this is not working, could you please open an issue with a minimal reproduction so we can investigate further?

[MKraust]

I think there could be a problem with raw rollup plugin.
I'm trying to build a simple React-to-PDF generator using Nitro. I need to import external (same with internal) CSS file as raw string

import mantineStyles from '@mantine/core/styles.css';

but facing this output

[nitro] rollup:before: 0.01ms
ℹ Building Nitro Server (preset: node-server)

[nitro 12:47:00 AM]  ERROR  Error: Could not load raw:@mantine/core/styles.css (imported by routes/index.tsx): ENOENT: no such file or directory, open '@mantine/core/styles.css'

But when I comment this line and use this plugin instead, then problem is gone.