a-x-
commented
1 year ago my error: ERR_INVALID_MODULE_SPECIFIER
``` cd server && yarn run start $ NODE_OPTIONS='--loader=ts-node/esm --experimental-specifier-resolution=node' ts-node -r tsconfig-paths/register --project tsconfig.json ./index.ts (node:88652) ExperimentalWarning: --experimental-loader is an experimental feature. This feature could change at any time (Use `node --trace-warnings ...` to show where the warning was created) (node:88652) ExperimentalWarning: The Node.js specifier resolution flag is experimental. It could change or be removed at any time. (node:88671) 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) /Users/wzhalmq/raif/ips-cortex-collateral-ui-application/node_modules/ts-node/dist-raw/node-internal-modules-esm-resolve.js:695 throw new ERR_INVALID_MODULE_SPECIFIER( ^ cd server && yarn run start $ NODE_OPTIONS='--loader=ts-node/esm --experimental-specifier-resolution=node' ts-node -r tsconfig-paths/register --project tsconfig.json ./index.ts (node:88652) ExperimentalWarning: --experimental-loader is an experimental feature. This feature could change at any time (Use `node --trace-warnings ...` to show where the warning was created) (node:88652) ExperimentalWarning: The Node.js specifier resolution flag is experimental. It could change or be removed at any time. (node:88671) 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) /Users/wzhalmq/raif/ips-cortex-collateral-ui-application/node_modules/ts-node/dist-raw/node-internal-modules-esm-resolve.js:695 throw new ERR_INVALID_MODULE_SPECIFIER( ^ CustomError: ERR_INVALID_MODULE_SPECIFIER @date-fns is not a valid package name /Users/wzhalmq/raif/ips-cortex-collateral-ui-application/shared/utils/date.ts ```More context
I have some esm only deps, some cjs only deps and some universal ones. Also I have some shared utils for node and browser.
I need paths in this case for implementing two date-fns adapter variants: for server and client:
shared/utils/date.server.ts:
export * from "date-fns";shared/utils/date.client.ts:
export * from "date-fns/esm";
aaggarwal-sumo
mettini
PavelGolodoniuc
Search Terms
what I found:
Expected Behavior
Take tsconfig.json paths into account even in esm mode. Keep imports, but transpile paths.
Actual Behavior
imports keeping as is in esm mode. One good thing I have: VSCode have not TS errors in this setup now, it was hard to accomplish it too.
Steps to reproduce the problem
{ "compilerOptions": { "paths": { "foo": "src/bar.ts" } } }ts-node-esm --project tsconfig.json src/index.tsimport foo from 'foo'and create some src/bar.ts file with default exportMinimal reproduction
will be later
Specifications
I have complex monorepo setup with 3 tsconfigs and many other things, I'll show later minimal repo if it really needed in this case... It's vitejs front and ts-node BFF for it I trying to implement now with shared utils.
server/tsconfig.json
```js { "compilerOptions": { "composite": true, // enable latest features "lib": ["esnext"], "module": "esnext", "target": "esnext", // if TS 5.x+ // https://www.typescriptlang.org/docs/handbook/release-notes/typescript-5-0.html#--moduleresolution-bundler "moduleResolution": "bundler", "allowImportingTsExtensions": true, "noEmit": true, "moduleDetection": "force", // "jsx": "react-jsx", // support JSX "allowJs": true, // allow importing `.js` from `.ts` "esModuleInterop": true, // allow default imports for CommonJS modules // best practices "strict": true, "forceConsistentCasingInFileNames": true, "skipLibCheck": true, // monorepo "paths": { "@date-fns": ["../shared/utils/date.server.ts"], "shared/*": ["../shared/*"], "@front/*": ["../src/*"] }, "baseUrl": ".", "plugins": [ { "name": "typescript-styled-plugin", "validate": false }, // Fix import absolute paths { "transform": "typescript-transform-paths", "useRootDirs": true }, // Transform paths in output .js files { "transform": "typescript-transform-paths", "useRootDirs": true, "afterDeclarations": true } // Transform paths in output .d.ts files (Include this line if you output declarations files) ], "rootDirs": [".", "../src", "../shared"], // other "types": ["jest"], "resolveJsonModule": true }, "ts-node": { // It is faster to skip typechecking. // Remove if you want ts-node to do typechecking. "transpileOnly": true, "esm": true, // import/export instead of require/module.exports "experimentalSpecifierResolution": "node", // omit .ts in imports "require": ["typescript-transform-paths/register", "tsconfig-paths/register"] }, "include": [ "./**/*", "./.eslintrc.cjs", "../jest.config.ts", // Don't include: "../src/utils/**/*", As it have browser specific, like utils/hooks.ts "../src/**/types.ts", "../src/**/config.ts", "../src/**/*.types.ts", "../src/**/*.d.ts", "../shared/**/*" ], "references": [{ "path": "../shared/tsconfig.json" }, { "path": "../src/tsconfig.json" }] } ```shared/tsconfig.json
```js { "compilerOptions": { "composite": true, // enable latest features "lib": ["esnext"], "module": "esnext", "target": "esnext", // if TS 5.x+ "moduleResolution": "bundler", // "allowImportingTsExtensions": true, // "noEmit": true, "moduleDetection": "force", // "jsx": "react-jsx", // support JSX "allowJs": true, "esModuleInterop": true, // best practices "strict": true, "forceConsistentCasingInFileNames": true, "skipLibCheck": true, "plugins": [ { "name": "typescript-styled-plugin", "validate": false }, // Fix import absolute paths { "transform": "typescript-transform-paths", "useRootDirs": true }, // Transform paths in output .js files { "transform": "typescript-transform-paths", "useRootDirs": true, "afterDeclarations": true } // Transform paths in output .d.ts files (Include this line if you output declarations files) ], "types": ["jest"], "resolveJsonModule": true, "paths": { "@date-fns": ["./utils/date.server.ts", "./utils/date.client.ts"] } }, "ts-node": { "transpileOnly": true, "require": ["typescript-transform-paths/register", "tsconfig-paths/register"] }, "include": ["./**/*"], "exclude": ["./.eslintrc.cjs"] } ```package.json (root)
```js { "name": "rbi-ips-toro-ui", "private": true, "type": "module", "scripts": { "dev": "yarn install && scripts/dev", "prod-server": "cd server && yarn run start", "build": "echo type check... && tsc && echo build front with vite... && vite build", "lint": "eslint src server shared", "mocks": "nodemon ./dev-server/devServer.js", "test": "NODE_OPTIONS=--experimental-vm-modules jest" }, "dependencies": { "@vitejs/plugin-react": "^3.1.0" "date-fns": "^2.29.3", "date-fns-tz": "^2.0.0", "lodash-es": "^4.17.21", "react": "17.0.2", "react-dom": "17.0.2", "react-router": "^6.2.1", "react-router-dom": "^6.2.1", // some deps are omitted }, "devDependencies": { "@jest/globals": "^29.5.0", "@typescript-eslint/eslint-plugin": "^5.59.1", "@typescript-eslint/parser": "^5.59.1", "esbuild": "^0.17.10", "esbuild-css-modules-plugin": "^2.7.1", "eslint": "^8.39.0", "eslint-config-react-app": "^7.0.1", "eslint-plugin-react-hooks": "^4.6.0", "eslint-plugin-unused-imports": "^2.0.0", "jest": "^29.5.0", "jest-environment-jsdom": "^29.5.0", "ts-jest": "^29.1.0", "ts-node": "^10.9.1", "tsconfig-paths": "^4.2.0", "typescript": "^5.0.4", "typescript-plugin-css-modules": "^3.4.0", "typescript-plugin-styled-components": "^2.0.0", "typescript-transform-paths": "^3.4.6", "vite": "^4.1.4", "vite-jest": "^0.1.4" // some deps are omitted } } ```shared/package.json
```js { "name": "shared", "type": "module", "version": "1.0.0", "main": "index.js", "license": "ICS", "private": true } ```src: package.json and tsconfig.json currently are not interesting as they using for client-side/front