4

I'm migrating my react app to typescript. It works fine now, But after adding typescript compiler and renaming files to .ts and .tsx, its throwing module not found. Any lead will be helpful. I have got the following dir structure.

| src
  | select.tsx
  | index.ts
  | WindowedSelect.tsx
  | MenuList.tsx
| demo
  | index.tsx
| webpack.config.demo.js
| webpack.config.js
| tsconfig.json
| package.json

I run demo/index (webpack.config.demo) for npm start command and src/index.tsx (webpack.config) for npm run build. But getting Moddule Not found error in both.

Error (npm start):

ERROR in ./demo/index.tsx
Module not found: Error: Can't resolve '../src/WindowedSelect'

Error (npm run build):

ERROR in ./src/index.ts
Module not found: Error: Can't resolve './MenuList'

ERROR in ./src/index.ts
Module not found: Error: Can't resolve './WindowedSelect'

The IntelliSense works fine and navigates to corresponding files on click. I don't understand what is the issue here.

PS: apart from the module not found error, there are also several type errors as this is a js project. The plan is to gradually migrate to typescript. So how to set the default severity to "warn" for type errors?

webpack.config.js

const path = require('path');

module.exports = {
  entry: './src/index.ts',
  output: {
    filename: 'main.js',
    path: path.resolve(__dirname, 'dist'),
    libraryTarget: 'commonjs2',
  },
  module: {
    rules: [
      {
        test: /\.(ts|tsx)$/,
        exclude: /node_modules/,
        use: {
          loader: "ts-loader"
        }
      }
    ]
  },
  externals: {
    react: 'commonjs react',
    'react-dom': 'commonjs react-dom'
  },
};

Edit: tsconfig.json

{
  "compilerOptions": {
    /* Visit https://aka.ms/tsconfig.json to read more about this file */

    /* Basic Options */
    // "incremental": true,                   /* Enable incremental compilation */
    "target": "es5",                          /* Specify ECMAScript target version: 'ES3' (default), 'ES5', 'ES2015', 'ES2016', 'ES2017', 'ES2018', 'ES2019', 'ES2020', or 'ESNEXT'. */
    "module": "commonjs",                     /* Specify module code generation: 'none', 'commonjs', 'amd', 'system', 'umd', 'es2015', 'es2020', or 'ESNext'. */
    "lib": [                                  /* Specify library files to be included in the compilation. */
      "DOM",
      "DOM.Iterable",
      "ESNext"
    ],
    "allowJs": true,                          /* Allow javascript files to be compiled. */
    // "checkJs": true,                       /* Report errors in .js files. */
    "jsx": "react",                           /* Specify JSX code generation: 'preserve', 'react-native', or 'react'. */
    // "declaration": true,                   /* Generates corresponding '.d.ts' file. */
    // "declarationMap": true,                /* Generates a sourcemap for each corresponding '.d.ts' file. */
    // "sourceMap": true,                     /* Generates corresponding '.map' file. */
    // "outFile": "./",                       /* Concatenate and emit output to single file. */
    // "outDir": "./",                        /* Redirect output structure to the directory. */
    // "rootDir": "./",                       /* Specify the root directory of input files. Use to control the output directory structure with --outDir. */
    // "composite": true,                     /* Enable project compilation */
    // "tsBuildInfoFile": "./",               /* Specify file to store incremental compilation information */
    // "removeComments": true,                /* Do not emit comments to output. */
    // "noEmit": true,                        /* Do not emit outputs. */
    // "importHelpers": true,                 /* Import emit helpers from 'tslib'. */
    // "downlevelIteration": true,            /* Provide full support for iterables in 'for-of', spread, and destructuring when targeting 'ES5' or 'ES3'. */
    "isolatedModules": true,                  /* Transpile each file as a separate module (similar to 'ts.transpileModule'). */

    /* Strict Type-Checking Options */
    "strict": false,                           /* Enable all strict type-checking options. */
    "noImplicitAny": false,                 /* Raise error on expressions and declarations with an implied 'any' type. */
    "strictNullChecks": false,              /* Enable strict null checks. */
    "strictFunctionTypes": false,           /* Enable strict checking of function types. */
    "strictBindCallApply": false,           /* Enable strict 'bind', 'call', and 'apply' methods on functions. */
    "strictPropertyInitialization": false,  /* Enable strict checking of property initialization in classes. */
    "noImplicitThis": false,                /* Raise error on 'this' expressions with an implied 'any' type. */
    "alwaysStrict": false,                  /* Parse in strict mode and emit "use strict" for each source file. */

    /* Additional Checks */
    // "noUnusedLocals": true,                /* Report errors on unused locals. */
    // "noUnusedParameters": true,            /* Report errors on unused parameters. */
    // "noImplicitReturns": true,             /* Report error when not all code paths in function return a value. */
    // "noFallthroughCasesInSwitch": true,    /* Report errors for fallthrough cases in switch statement. */

    /* Module Resolution Options */
    // "moduleResolution": "node",            /* Specify module resolution strategy: 'node' (Node.js) or 'classic' (TypeScript pre-1.6). */
    // "baseUrl": "./",                       /* Base directory to resolve non-absolute module names. */
    // "paths": {},                           /* A series of entries which re-map imports to lookup locations relative to the 'baseUrl'. */
    // "rootDirs": [],                        /* List of root folders whose combined content represents the structure of the project at runtime. */
    // "typeRoots": [],                       /* List of folders to include type definitions from. */
    // "types": [],                           /* Type declaration files to be included in compilation. */
    // "allowSyntheticDefaultImports": true,  /* Allow default imports from modules with no default export. This does not affect code emit, just typechecking. */
    "esModuleInterop": true,                  /* Enables emit interoperability between CommonJS and ES Modules via creation of namespace objects for all imports. Implies 'allowSyntheticDefaultImports'. */
    // "preserveSymlinks": true,              /* Do not resolve the real path of symlinks. */
    // "allowUmdGlobalAccess": true,          /* Allow accessing UMD globals from modules. */

    /* Source Map Options */
    // "sourceRoot": "",                      /* Specify the location where debugger should locate TypeScript files instead of source locations. */
    // "mapRoot": "",                         /* Specify the location where debugger should locate map files instead of generated locations. */
    // "inlineSourceMap": true,               /* Emit a single file with source maps instead of having a separate file. */
    // "inlineSources": true,                 /* Emit the source alongside the sourcemaps within a single file; requires '--inlineSourceMap' or '--sourceMap' to be set. */

    /* Experimental Options */
    // "experimentalDecorators": true,        /* Enables experimental support for ES7 decorators. */
    // "emitDecoratorMetadata": true,         /* Enables experimental support for emitting type metadata for decorators. */

    /* Advanced Options */
    "skipLibCheck": true,                     /* Skip type checking of declaration files. */
    "forceConsistentCasingInFileNames": true  /* Disallow inconsistently-cased references to the same file. */
  }
}

5
  • 1
    What is the complier to build your code? If you use webpack to build your code, you have to share your webpack config (what is the typescript loader in this case) Commented Sep 21, 2020 at 14:57
  • @tmhao2005 I was using babel to and webpack for converting to compile. Added ts-loader as part of migration. Edit: Added code for web pack now Commented Sep 21, 2020 at 15:02
  • If you use ts loader, can you also share your tsconfig as well? Commented Sep 21, 2020 at 15:04
  • Everything looks right so far. But not sure what is the command coming up with the error? Commented Sep 21, 2020 at 15:20
  • the npm run build command runs the script "build": "webpack", and npm start runs "start": "webpack-dev-server --mode development --config webpack.demo.config.js", defined in package.json Commented Sep 21, 2020 at 15:26

2 Answers 2

8

It sounds like the issue is likely from missing to point out the resolve extensions in webpack.config. Try to add more that property:

resolve: {
  extensions: ['.ts', '.tsx', '.js', '.jsx'],    
},
Sign up to request clarification or add additional context in comments.

2 Comments

Damn.. that was it. Thanks a lot for your help. But still am not able to build the app due to type errors. Currently, the app doesn't have any type definition for any component. So can these errors be suppressed for the ease-of transition to ts?
Generally you have to fill the types for them all but if you want to quickly skip type checking, apart from disable strict mode and other relevant configuration I think you can put // @ts-nocheck on the top of each file to stop checking for entire file
0

This is what worked for me after a few hours searching:

npm install --save-dev typescript @types/node @types/react @types/react-dom @types/jest --force

Then I created a tsconfig.json file and pasted the following code:

{
  "compilerOptions": {
    "target": "es5",
    "lib": ["dom", "dom.iterable", "esnext"],
    "allowJs": true,
    "skipLibCheck": true,
    "esModuleInterop": true,
    "allowSyntheticDefaultImports": true,
    "strict": true,
    "forceConsistentCasingInFileNames": true,
    "noFallthroughCasesInSwitch": true,
    "module": "esnext",
    "moduleResolution": "node",
    "resolveJsonModule": true,
    "isolatedModules": true,
    "noEmit": true,
    "jsx": "react-jsx"
  },
  "include": ["src"]
}

Finally, I restarted the app.

1 Comment

i wonder if this is recommended for those who started with create react app

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.