Configuration Languages: TS_NODE_PROJECT not working #2733

Activity

1. SeanPercy commented on Jan 11, 2019

   

   SeanPercy

   on Jan 11, 2019

   More actions

   @akopchinskiy I faced a similar issue. The following worked for me:

   • run npm i cross-env
   • change the script to "build": "cross-env TS_NODE_PROJECT=\"tsconfig-for-webpack-config.json\" webpack"

   ❤️React with ❤️3Reacted by Ercin Dedeoglu, 서동민 and Erin
2. EugeneHlushko commented on Jan 14, 2019

   

   EugeneHlushko

   on Jan 14, 2019

   Contributor

   More actions

   @akopchinskiy can you confirm that adding cross-env like Sean suggests solves your issue?
3. akopchinskiy commented on Jan 14, 2019

   

   akopchinskiy

   on Jan 14, 2019

   Author

   More actions

   @EugeneHlushko yes it's working.
   But there is another problem with it: webpack.config.json uses global environments and when I use cross-env TS_NODE_PROJECT=... one of my webpack configs conmpiled incorrectly, because I have different tsconfig.json's as well.
4. akopchinskiy

   closed this as completedon Jan 14, 2019
5. SeanPercy commented on Jan 14, 2019

   

   SeanPercy

   on Jan 14, 2019

   Last edited by SeanPercy

   More actions

   @akopchinskiy I guess you mean something like setting the mode to production / development, right?

   This is my folder structure:

       |-- dist
       |-- node_modules
       |-- src
       |-- tests
           |-- testProductionBuild.ts
       |-- tools
           |-- .stylelintrc
           |-- babel.config.js
           |-- nodemon.json
           |-- tslint.json
           |-- tsconfig-for-webpack-config.json
           |-- webpackConfig
               |-- common.ts
               |-- development.ts
               |-- production.ts
       |-- .babelrc
       |-- .env
       |-- .gitignore
       |-- package-lock.json
       |-- package.json
       |-- tsconfig.json
       |-- webpack.config.ts
   
    
   

   And here is an excerpt of my package.json

     "scripts": {
       "webpack-ts": "cross-env TS_NODE_PROJECT=%npm_package_config_TS_NODE_PROJECT%",
       "build": "npm run webpack-ts NODE_ENV=production webpack",
       "pretest-build": "npm run build",
       "test-build": "ts-node --project %npm_package_config_TS_NODE_PROJECT% tests/testProductionBuild.ts",
       "server": "npm run webpack-ts NODE_ENV=development webpack-dev-server",
     },
     "config": {
       "TS_NODE_PROJECT": "\"tools/tsconfig-for-webpack-config.json\""
     },
   

   The tsconfig.json file on the root level is used by my IDE and tslint for linting the entire project.
   The tools/tsconfig-for-webpack-config.json file is only used to run webpack.config.ts and test/testProductionBuild.ts
6. hakobpogh commented on May 15, 2019

   

   hakobpogh

   on May 15, 2019

   More actions

   Hi there. I have a .ts config in two different projects one is with the following versions:

       "webpack": "^4.29.0",
       "webpack-cli": "^3.2.1"
   

   and the other is with the following versions:

       "webpack": "^4.31.0",
       "webpack-cli": "^3.3.2"
   

   But for the first one I don't need to add TS_NODE_PROJECT=\"tsconfig-for-webpack-config.json\" but for the second one, it's required. I think that it's better to make it work without this additional stuff.
7. aryzing commented on Aug 24, 2019

   

   aryzing

   on Aug 24, 2019

   Contributor

   More actions

   @hakobpogh how, then, can you use different TypeScript configs for webpack and for your code?

   👍React with 👍1Reacted by Eduard Malakhov

   👀React with 👀1Reacted by Matei Radu
8. eduard-malakhov commented on May 1, 2020

   

   eduard-malakhov

   on May 1, 2020

   Last edited by eduard-malakhov

   More actions

   @aryzing, though this is an old issue, maybe this would still be useful. I've had the exact same issue and I managed to resolve it by adding delete process.env.TS_NODE_PROJECT; at the top of my webbacp.config.ts as suggested in jonaskello/tsconfig-paths-webpack-plugin#17. This hack basically clears the TS_NODE_PROJECT variable for any code inside the config, including ts-loader which will then use the default tsconfig.json.
9. wrightwriter commented on Aug 18, 2023

   

   wrightwriter

   on Aug 18, 2023

   More actions

   I solved this by modifying my tsconfig as per the docs

   {
     "compilerOptions": {
        // stuff
     }
     "ts-node": {
       "compilerOptions": {
         "module": "CommonJS",
         "target": "ESNext",
         "esModuleInterop": true,
         "moduleResolution": "node",
         "verbatimModuleSyntax": false
       }
     },
   }

   👍React with 👍1Reacted by Cheikhna Diouf