Definitelytyped: Cannot find module 'csstype'

Try compilerOptions.moduleResolution: "node"

(Edit by Orta: If you are seeing this inside DefinitelyTyped, you need to run npm install in the dependency where you are seeing that error. E.g. cd types/react; npm install and then listing should be better - see https://github.com/microsoft/dtslint/issues/226 )

I had this error as well.

moduleResolution: true gives me errors - and isn't listed in the docs as a valid value - but setting moduleResolution: "node" looks like it has done the job 👍 Thanks!

Sorry, I meant to say "node" 😆 Changed my comment. Glad it helped.

Set "moduleResolution": "node" is useful for me, too.

Thanks Frenic. Works for me as well.

Can anyone provide color on why? Is there an update that would make setting this unnecessary?

If compilerOptions.module === "AMD" or "System" or "ES6" the default for compilerOptions.moduleResolution would be "Classic", otherwise it's "Node". So if you use one of these module strategies, but have all your packages under node_modules. The compilerOptions.moduleResolution must be set to "Node".

For Classic:

For non-relative module imports, however, the compiler walks up the directory tree starting with the directory containing the importing file, trying to locate a matching definition file.

For Node:

Node will look for your modules in special folders named node_modules. A node_modules folder can be on the same level as the current file, or higher up in the directory chain. Node will walk up the directory chain, looking through each node_modules until it finds the module you tried to load.

(source)

"module": "commonjs" fixed this issue for me, try it.

For those using classic module resolution who _don't_ want to change to node module resolution, I was able to get around this problem by adding a paths entry for csstype in my tsconfig.json, since my project is using the baseUrl config option. See baseUrl documentation for more details.

Obviously, this is not a scalable approach if you have many conflicts like this, but this was our first and this has at least bought us some time if we want to consider switching over to node module resolution.

I was running into this as well.

Via WebPack + TypeScript

Module not found: Error: Can't resolve 'csstype' 

What fixed it for me, which is likely pretty hackey, but as of TS 2.9 you can import() types (https://blogs.msdn.microsoft.com/typescript/2018/05/31/announcing-typescript-2-9/#import-types), so I did this and it compiles now without complaint:

type VisibilityProperty = import('csstype').VisibilityProperty;
type AnimationProperty = import('csstype').AnimationProperty;

Hi. Thanks for the suggestion here of setting compilerOptions.moduleResolution: "node".
However unfortunately, the moduleResolution is already set as "node" when I created the project using create-react-app-typescript but I am still seeing the problem.

I will keep on checking but would be great if someone already knew the answer and can tell me how to fix it :-)

UPDATE: sorry it is my bad setting - there is an tsconfig.test.json that has module set as commonjs and adding "moduleResolution": "node" seems to have fixed it.

I am checking out types/react-tag-autocomplete and running npm run lint react-tag-autocomplete. Getting same error, error TS2307: Cannot find module 'csstype'.

After adding "moduleResolution": "node", in compilerOptions of react-tag-complete's tsconfig.json, it gives error: Error: Unexpected compiler option moduleResolution.

Any help?

This drove me nuts trying to author a type definition that depended on react. It turns out that the csstype library has its own TS definitions, which are thus not present in the /types directory of this repo. I created an issue in dtslint to address this:

https://github.com/Microsoft/dtslint/issues/226

For me, setting the moduleResolution param didn't work, so I manually performed the solution to which @mike-marcacci had already suggested at the PR he raised at the dtslint repo:

cd types/react
npm i

@Rahul-Sagore I'm getting the same error as you. Did you ever figure out how to resolve this?

@mcmar Nope.

@Rahul-Sagore I'm getting the same error as you. Did you ever figure out how to resolve this?

You have to install dependencies of types/react and that will work :)

as indicated in this reply https://github.com/DefinitelyTyped/DefinitelyTyped/issues/24788#issuecomment-495861835

I also have this issue.

1. Setting "moduleResolution": "node", give me error Error: Unexpected compiler option moduleResolution
2. I've tried to

    cd types\react
    npm i

Then running npm run lint <my-package> shows me huge amount of errors with csstype like

../react/node_modules/csstype/index.d.ts(2071,31): error TS1005: '(' expected.
../react/node_modules/csstype/index.d.ts(2083,19): error TS2693: 'LetterSpacingProperty' only refers to a type, but is being used as a value here.
../react/node_modules/csstype/index.d.ts(2083,49): error TS1005: '(' expected.
../react/node_modules/csstype/index.d.ts(2096,15): error TS2693: 'LineBreakProperty' only refers to a type, but is being used as a value here.

And several hundreds of similar lines

Same error as @fyodore82 after performing steps 1/2

Solve it by writing "node" with a capital "N":

"moduleResolution": "Node"

Works on our side.

https://www.typescriptlang.org/docs/handbook/compiler-options.html

The "moduleResolution": "Node" solution didn't fix it for me, but going into the /types/react directory and running npm install resolved the issue.