Alisson Cavalcante Agiani
Alisson Cavalcante Agiani
Hey @virtuallyunknown , I forgot to say I run this script with [tsx](https://github.com/esbuild-kit/tsx), which automaticallly solves lots of ESM problems
Also sharing my base tsconfig.json for science: ```ts { "compilerOptions": { "target": "esnext", "incremental": true, "composite": true, "module": "esnext", "moduleResolution": "node", "inlineSourceMap": true, "noEmit": true, "noUnusedLocals": true, "noUnusedParameters": true, "noImplicitReturns":...
Yeah I gave up on moduleResolution: "nodenext" because it doesn't seem to respect allowSyntheticDefaultImports: true
Still having problems with this. There is no workaround?
In limited cloud environments like Google App Engine you don't have the luxury of PNPM and the environment strips the node_modules folder and forces a npm install, which doesn't recognize...
It's what I said above, limited cloud environments like Google force the `npm install` after transferring the files.
I tried adapting the starter to use it, but didn't had knowledge enough so the build was breaking, some tasks weren't working
Oh and I got a bit confused about the filesystem autorouting, how to automatically add /resource/:id pages for example
But if you use React Router with vite-plugin-ssr you miss the autorouting, right?
well, let's wait the Vite fix, maybe I can try again