Repository navigation
syntax error in custom.typings.d.ts #828
Description
Activity
IntelliJ has been complaining about this for me as well. I'd love to know what's the proper way of resolving this..
I have a related problem with
declare module "*";, when included my WebStorm fails to provide TypeScript support for all other modules, and trying to jump any module results in jumping to this line. Is this line necessary?Awesome, thanks.
I'm also getting
Unresolved typeon things likePromiseandrequire. I feel like these recent changes aren't quite usable for us yet so we'll be using 759e9ee to seed new projects for now. Hopefully these problems won't deter new adopters looking for a "turn-key" seed.Did you try VS Code
I had the same problem, I changed tsdk used by VS Code to point to Typescript 2.0, ie in the node modules folder, you can do that per workspace no unresolved types in Vs Code nowDoes ee0c85e resolves your issue?
Using visual studio 2015 with typescript 2.02 beta, this problem still exists.
Currently the first non-comment line in custom.d.ts is as follows
declare module "*";but that seems to give a syntax error on the semicolon with the message '{ expected', as the compiler expects a curly brace. Changing it to the following seems to fix it
declare module "*" {}Is that a valid fix?