Webpack compilation issues? about react HOT 3 CLOSED

@JMStudiosJoe There may be a better solution that this (the best being to fix the implicit any types in the core), but adding "skipLibCheck": true to your project's tsconfig.json should suppress these errors.

from react.

So, I took a look at the code. The problem here is the fact that the ui-router-core lib is developed with the noImplicitAny default value, which is false, while your config sets it to true. This is why the core lib compiles fine in the source but doesn't in your setup.

That being said, you can fix the problem (for now) by setting "noImplicitAny": false in your tsconfig.json and let TS deal with implicit any types, unless you prefer skipping the whole lib check and in that case you can do what @warrenseymour suggests.

I guess the core lib should support your configuration and we should make a PR to explicitly set the any type on those variables.

from react.

@warrenseymour and @elboman thank you both for fast responses and both solutions worked to let you know.

from react.