process is not defined

[nktnet1]

process is not defined

[fonziemedia]

Hey thanks for the quick response.

I'm indeed trying to run it for a frontend application running node 20.8.0 with vite

I guess I'll have to look for for another way to go around the issues I'm experiencing but thanks anyway :)

[fonziemedia]

Hey @nktnet1

Thanks for the suggestion but it seems require-esm-in-cjs is also server-side only..

By the way, the error I was getting was actually related to vite:
vitejs/vite#1973

I've managed to fix it but then I started getting other errors related to node.. 🤷 I guess I'll just have to do some refactoring of the project..

Thanks again for your help!

[nktnet1]

Hi @fonziemedia,

Thank you for reaching out.

Could you provide a minimal reproducible example for this issue? Other information such as your node version and the content of your package.json would help.

Note that unfortunately, import-sync only works with NodeJS (server-side), not client-side (e.g. frontend development and the like) see below. If your project is indeed NodeJS, please first confirm that you are able to access NodeJS process - e.g. as simple as

console.log(process);

Finally, the error suggests that the issue may lie with the esm module, a dependency of import-sync. It may be worth it to look through the issues in that project too to see if there are any workarounds :).

[nktnet1]

@fonziemedia you can maybe try your luck with this module

• https://www.npmjs.com/package/require-esm-in-cjs

although there are some performance implications to consider, for example as a result of using deasync. Hope this points you in the right direction though :).

[nktnet1]

Found this fork of fractal that uses Vite and import-sync together:

• https://github.com/Schleuse/fractal

so I'm not so sure about my comment regarding only server-side NodeJS anymore 🤷

e.g. it's being used here in ./packages/react/src/adapter.js#L13:

• https://github.com/Schleuse/fractal/blob/a05bde7c8cb2788e296f5ffda859e46debbbcd39/packages/react/src/adapter.js#L13

Maybe there is a configuration somewhere that allows the esm module to work.

Also found some workarounds:

• https://stackoverflow.com/a/75633477/22324694
• https://dev.to/boostup/uncaught-referenceerror-process-is-not-defined-12kg