Theo's Typesafe Cult•12mo ago

`env.mjs` as opposed to `env.cjs` or `env.js`

Heya, is there a reason why the env definition is in an mjs file as opposed to cjs or simply js? Reason I'm asking is because I'm trying to setup websockets and mjs won't work as we're compiling with commonjs.

6 Replies

Sybatron•12mo ago

you should be able able to put them in .ts too

mrlowlevel•12mo ago

I think the reason ts doesn't work is because of this line in next.config.mjs

!process.env.SKIP_ENV_VALIDATION && (await import('./src/env.mjs'))

!process.env.SKIP_ENV_VALIDATION && (await import('./src/env.mjs'))

dan•12mo ago

I'm assuming this is the old env setup. But iirc the env is imported in the next.config.mjs and you cant import ts into that (or commonjs iirc) Either that or mjs is used because modules are just better :3

mrlowlevel•12mo ago

yeah our t3 init version is 7.5.1 let me see if anything breaks if I just convert env.mjs to env.js in all the places ok yeah then next gets mad

import { z } from 'zod'
^^^^^^

SyntaxError: Cannot use import statement outside a module

import { z } from 'zod'
^^^^^^

SyntaxError: Cannot use import statement outside a module

Sybatron•12mo ago

you have to change the imports to require if you do commonjs import is only for modules

mrlowlevel•12mo ago

yah indeed testing that now

Gaming

Programming

`env.mjs` as opposed to `env.cjs` or `env.js`