Closed jmrapp1 closed 5 years ago
You have no include
or files
in your tsconfig.json
, therefore the compiler/editor has no idea which files to apply the configuration to.
@kitsonk Even if I add it it still does not work. It's always worked without that included also. The issue is also completely separate from the IDE. When I push my changes to Heroku that can not build the project either and continuously fails.
Your version of TypeScript is pinned at "3.0.1"
, so why do you think it was a change to TypeScript and not something else in your build toolchain that caused the issue? The version of TypeScript did not change with a fresh install.
@kitsonk Should have mentioned I was playing around with the package versions to see if it was bumped. It was at ~2.8.3
And reverting to version 2.8.3
or 2.9.2
fixes the issue?
@kitsonk No neither does :/
Yeah, so again, I don't think you are dealing with a TypeScript issue, you are dealing with something else that is fragile in your toolchain.
@kitsonk Strange, yeah I'll keep looking into it and see if I find out what's causing the issue
@kitsonk setting up a sample project with only typescript
as a dependency I can easily reproduce the issue.
TypeScript Version: 3.0.1
Search Terms: Expiremental Decorator not being recognized in tsconfig
Code tsconfig
Expected behavior: To recognize experimental decorators
Actual behavior: Throwing error on all files containing decorators:
TS1219: Experimental support for decorators is a feature that is subject to change in a future release. Set the 'experimentalDecorators' option to remove this warning.
Some background, this issue came out of no where. ~20 hours ago I was able to do a clean
npm install
and build the project without any issue. This morning, I ran the same command with no change to any packages, tsconfig, or related code and this error started occurring. All of the issues I have found online are only related to the error occurring in VSCode, but that's no help to me because I am using Webstorm.The fact that it worked last night but not this morning makes me think there's some update to a package (potentially TS) that is causing the issue to occur.
Package.json