Experimental decorators warning in TypeScript compilation
I have
Experimental support for decorators is a feature that is subject to change in a future release. Set the 'experimentalDecorators' option `to remove this warning.
even my compilerOptions in tsconfig.json have settings:
"emitDecoratorMetadata": true,
"experimentalDecorators": true,
What is weird that some random classes that use decorators does not show that warning but rest in same project does.
What could cause such behaviorof the TypeScript compiler?
typescript decorator visual-studio-code
|
show 1 more comment
I have
Experimental support for decorators is a feature that is subject to change in a future release. Set the 'experimentalDecorators' option `to remove this warning.
even my compilerOptions in tsconfig.json have settings:
"emitDecoratorMetadata": true,
"experimentalDecorators": true,
What is weird that some random classes that use decorators does not show that warning but rest in same project does.
What could cause such behaviorof the TypeScript compiler?
typescript decorator visual-studio-code
3
Have you tried restarting VS Code? I've found that's necessary after making tsconfig.json changes sometimes.
– David Sherret
Jul 8 '16 at 16:26
Yes - I did it a few times - only difference is that different file is not having warning but others still
– bensiu
Jul 8 '16 at 16:38
2
You can try blow answer dude. It work for me! stackoverflow.com/a/38970591/2468781
– erdemildiz
May 10 '17 at 18:20
3
By chance if someone else runs into this that is using VS Professional, not VS Code, you may have added a.ts
file to an angular project manually; if so, the default TS compilation is conflicting with Angular CLI. Right-click the file -> Properties -> Build Action : None. Then restart VS if needed.
– pbarranis
Jul 19 '18 at 14:16
VS Code restart helped me solve the issue.
– CMA
Nov 6 '18 at 6:28
|
show 1 more comment
I have
Experimental support for decorators is a feature that is subject to change in a future release. Set the 'experimentalDecorators' option `to remove this warning.
even my compilerOptions in tsconfig.json have settings:
"emitDecoratorMetadata": true,
"experimentalDecorators": true,
What is weird that some random classes that use decorators does not show that warning but rest in same project does.
What could cause such behaviorof the TypeScript compiler?
typescript decorator visual-studio-code
I have
Experimental support for decorators is a feature that is subject to change in a future release. Set the 'experimentalDecorators' option `to remove this warning.
even my compilerOptions in tsconfig.json have settings:
"emitDecoratorMetadata": true,
"experimentalDecorators": true,
What is weird that some random classes that use decorators does not show that warning but rest in same project does.
What could cause such behaviorof the TypeScript compiler?
typescript decorator visual-studio-code
typescript decorator visual-studio-code
edited Nov 23 '17 at 17:21
peterh
6,320154770
6,320154770
asked Jul 8 '16 at 16:15
bensiubensiu
13k225486
13k225486
3
Have you tried restarting VS Code? I've found that's necessary after making tsconfig.json changes sometimes.
– David Sherret
Jul 8 '16 at 16:26
Yes - I did it a few times - only difference is that different file is not having warning but others still
– bensiu
Jul 8 '16 at 16:38
2
You can try blow answer dude. It work for me! stackoverflow.com/a/38970591/2468781
– erdemildiz
May 10 '17 at 18:20
3
By chance if someone else runs into this that is using VS Professional, not VS Code, you may have added a.ts
file to an angular project manually; if so, the default TS compilation is conflicting with Angular CLI. Right-click the file -> Properties -> Build Action : None. Then restart VS if needed.
– pbarranis
Jul 19 '18 at 14:16
VS Code restart helped me solve the issue.
– CMA
Nov 6 '18 at 6:28
|
show 1 more comment
3
Have you tried restarting VS Code? I've found that's necessary after making tsconfig.json changes sometimes.
– David Sherret
Jul 8 '16 at 16:26
Yes - I did it a few times - only difference is that different file is not having warning but others still
– bensiu
Jul 8 '16 at 16:38
2
You can try blow answer dude. It work for me! stackoverflow.com/a/38970591/2468781
– erdemildiz
May 10 '17 at 18:20
3
By chance if someone else runs into this that is using VS Professional, not VS Code, you may have added a.ts
file to an angular project manually; if so, the default TS compilation is conflicting with Angular CLI. Right-click the file -> Properties -> Build Action : None. Then restart VS if needed.
– pbarranis
Jul 19 '18 at 14:16
VS Code restart helped me solve the issue.
– CMA
Nov 6 '18 at 6:28
3
3
Have you tried restarting VS Code? I've found that's necessary after making tsconfig.json changes sometimes.
– David Sherret
Jul 8 '16 at 16:26
Have you tried restarting VS Code? I've found that's necessary after making tsconfig.json changes sometimes.
– David Sherret
Jul 8 '16 at 16:26
Yes - I did it a few times - only difference is that different file is not having warning but others still
– bensiu
Jul 8 '16 at 16:38
Yes - I did it a few times - only difference is that different file is not having warning but others still
– bensiu
Jul 8 '16 at 16:38
2
2
You can try blow answer dude. It work for me! stackoverflow.com/a/38970591/2468781
– erdemildiz
May 10 '17 at 18:20
You can try blow answer dude. It work for me! stackoverflow.com/a/38970591/2468781
– erdemildiz
May 10 '17 at 18:20
3
3
By chance if someone else runs into this that is using VS Professional, not VS Code, you may have added a
.ts
file to an angular project manually; if so, the default TS compilation is conflicting with Angular CLI. Right-click the file -> Properties -> Build Action : None. Then restart VS if needed.– pbarranis
Jul 19 '18 at 14:16
By chance if someone else runs into this that is using VS Professional, not VS Code, you may have added a
.ts
file to an angular project manually; if so, the default TS compilation is conflicting with Angular CLI. Right-click the file -> Properties -> Build Action : None. Then restart VS if needed.– pbarranis
Jul 19 '18 at 14:16
VS Code restart helped me solve the issue.
– CMA
Nov 6 '18 at 6:28
VS Code restart helped me solve the issue.
– CMA
Nov 6 '18 at 6:28
|
show 1 more comment
21 Answers
21
active
oldest
votes
Although VS Code is a great editor for TypeScript projects, it needs a kick every now and again. Often, without warning, certain files cause it to freak out and complain. Mostly the fix seems to be to save and close all open files, then open tsconfig.json
. After that you should be able to re-open the offending file without error. If it doesn't work, lather, rinse, and repeat.
If your tsconfig.json
specifies its source files using the files
array, IntelliSense will only function correctly if the file in question is referenced such that VS Code can find it by traversing the input file tree.
Edit: The 'reload window' command (added ages ago now) should solve this problem once and for all.
4
Thank you - removing "files" from tsconfig.json resolve problem
– bensiu
Jul 11 '16 at 14:35
2
The answer was not really relevant to my case but somehow helped my figure out my problem. I am using VS 2015 and between changing thexproj
andtsconfig
file, I missed the fact that the folder with my script files was listed in theexclude
section oftsconfig
. Hope this helps someone.
– Stefan Balan
Sep 3 '16 at 18:10
5
File > Close folder > Open folder worked for me. This happened after I restarted the machine without properly closing vscode.
– Adrian Moisa
Mar 24 '17 at 12:28
2
What if i am not using typescript? Only javascript es6?
– Azarus
Apr 22 '17 at 22:17
3
I'm not sure when it was added but the command palette now has "Reload Window", which is ideal for this sort of thing.
– Coderer
Aug 7 '17 at 6:46
|
show 5 more comments
I've to add the following in the settings.json file of vscode to remove the warning.
"javascript.implicitProjectConfig.experimentalDecorators": true
VSCode -> Preferences -> Settings
Thanks a lot. I'm using es6+decorators and have not typescript installed. Awesome.
– Achmedzianov Danilian
Jan 18 '18 at 11:56
2
This answer is the best, because there's no need to create a separated file in the project to solve a VSCode issue.
– Rodrigo
Mar 14 '18 at 3:22
ctrl + ,
shortcut key to open usersettings. on usersettings click 3 dots (...
) then on pop up clickOpen settings.json
to opensettings.json
– simple_human
Oct 3 '18 at 9:37
add a comment |
This error also occurs when you choose "src" folder for your workspace folder.
When the root folder, folder where the "src", "node_modules" are located is chosen, the error disappears
5
Came here to post this. This fixed it for me. I was using Angular 2 via Angular CLI.
– async
Jun 30 '17 at 12:17
4
This worked for me on Visual Studio Code. Thanks !
– franpen
Oct 11 '17 at 13:53
add a comment |
have to add typescript.tsdk
to my .vscode/settings.json
:
"typescript.tsdk": "node_modules/typescript/lib"
4
This solved the issue for me, but that line goes into.vscode/settings.json
as per this
– Fran Rodriguez
Sep 20 '16 at 16:42
1
Also solved it for me, but I didn't have the.vscode
folder (I don't know why - I'm a backend dev, leave me alone!), so I created one in the root folder with saidsettings.json
file.
– cr4ne
May 10 '17 at 6:13
add a comment |
inside your project create file tsconfig.json , then add this lines
{
"compilerOptions": {
"experimentalDecorators": true,
"allowJs": true
}
}
add a comment |
"javascript.implicitProjectConfig.experimentalDecorators": true
Will solve this problem.
add a comment |
Open settings.json
file in the following location <project_folder>/.vscode/settings.json
or you can open the file from the menu as mentioned below
VSCode -> File -> Preferences -> Workspace Settings
Then add the following lines in settings.json
file
{
"typescript.tsdk": "node_modules/typescript/lib",
"enable_typescript_language_service": false
}
That's all. You will see no warning/error regarding 'experimentalDecorators'
10
I got "Unknown configuration setting" after adding "enable_typescript_language_service" using vscode 1.8.1
– David Cheung
Jan 22 '17 at 12:35
2
This is HORRIBLE advice if your project uses Typescript!
– paulsm4
Jan 3 at 17:22
add a comment |
This answer is intended for people who are using a Javascript project and not a Typescript one. Instead of a tsconfig.json file you may use a jsconfig.json file.
In the particular case of having the decorators warning you wan write inside the file:
{
"compilerOptions": {
"experimentalDecorators": true
}
}
Fort the buggy behaviors asked, it's always better to specify the "include" in the config file, and restart the editor. E.g.
{
"compilerOptions": {
"target": "ES6",
"experimentalDecorators": true
},
"include": [
"app/**/*"
],
"exclude": [
"node_modules"
]
}
add a comment |
Add following lines in tsconfig.json and restart VS Code.
{
"compilerOptions": {
"experimentalDecorators": true,
"target": "es5",
"allowJs": true
}
}
The restart was the key for me. Thanks.
– rynop
Jan 10 at 5:34
add a comment |
Not to belabor the point but be sure to add the following to
- Workspace Settings not User Settings
under File >> Preferences >> Settings
"javascript.implicitProjectConfig.experimentalDecorators": true
this fixed the issue for me, and i tried quite a few suggestions i found here and other places.
add a comment |
For the sake of clarity and stupidity.
1) Open .vscode/settings.json.
2) Add "typescript.tsdk": "node_modules/typescript/lib" on it.
3) Save it.
4) Restart Visual Studio Code.
add a comment |
Please check you oppened in your VS Code the folder of the entire project and not only the src folder, because if you open only the src, then ts.config.json (located in the project folder) file will not be in scope, and VS will not recognize the experimental decorators parameters.
In my case this fixed all the problems related to this issue.
This was also my issue. Can you see node_modules? Can you see tsconfig.json? If not, open a new vsCode window, close the old window, choose file-->open folder, and make sure you select the parent folder ofsrc
andnode_modules
, rather than selecting justsrc
.
– Kyle Vassella
Feb 13 at 23:40
add a comment |
If you are working in Visual studio. You can try this fix
- Unload your project from visual studio
- Go to your project home directory and Open "csproj" file.
Add TypeScriptExperimentalDecorators to this section as shown in image
- Reload the project in Visual studio.
see more details at this location.
add a comment |
I corrected the warning by removing "baseUrl": "", from the tsconfig.json file
add a comment |
Open entire project's folder instead of project-name/src
tsconfig.json is out of src folder
add a comment |
- Open VScode.
- Press ctrl+comma
- Follow the directions in the screen shot
- Search about
experimentalDecorators - Edit it
- Search about
add a comment |
I had this problem recently under Visual Studio 2017 - turned out it was caused by a "feature" of VS - ignoring tsconfig.json when Build action is not set to Content.
So changing the Build action to Content and reloading the solution solved the problem.
add a comment |
You might run into this issue if you open a TS file that exists outside of the project. For instance, I'm using lerna and had a file open from another package. Although that other package had it's own tsconfig with experimental decorators, VsCode doesn't honor it.
add a comment |
I faced the same issue while creating an Injectable Services in Angular 2.
I have all the things at place in tsconfig.json .Still I was getting this error at ColorsImmutable line.
@Injectable()
export class ColorsImmutable {
And fix was to register the Service at module Level or Component Level
using the providers array.
providers:[ColorsImmutable ],
add a comment |
I added this option to tsconfig.json, "baseUrl": "front-end"
Replace front-end with the name of your angular-cli project.
add a comment |
If you are using cli to compile *.ts files, you can set experimentalDecorators using the following command:
tsc filename.ts --experimentalDecorators "true"
add a comment |
protected by eyllanesc May 6 '18 at 13:25
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
21 Answers
21
active
oldest
votes
21 Answers
21
active
oldest
votes
active
oldest
votes
active
oldest
votes
Although VS Code is a great editor for TypeScript projects, it needs a kick every now and again. Often, without warning, certain files cause it to freak out and complain. Mostly the fix seems to be to save and close all open files, then open tsconfig.json
. After that you should be able to re-open the offending file without error. If it doesn't work, lather, rinse, and repeat.
If your tsconfig.json
specifies its source files using the files
array, IntelliSense will only function correctly if the file in question is referenced such that VS Code can find it by traversing the input file tree.
Edit: The 'reload window' command (added ages ago now) should solve this problem once and for all.
4
Thank you - removing "files" from tsconfig.json resolve problem
– bensiu
Jul 11 '16 at 14:35
2
The answer was not really relevant to my case but somehow helped my figure out my problem. I am using VS 2015 and between changing thexproj
andtsconfig
file, I missed the fact that the folder with my script files was listed in theexclude
section oftsconfig
. Hope this helps someone.
– Stefan Balan
Sep 3 '16 at 18:10
5
File > Close folder > Open folder worked for me. This happened after I restarted the machine without properly closing vscode.
– Adrian Moisa
Mar 24 '17 at 12:28
2
What if i am not using typescript? Only javascript es6?
– Azarus
Apr 22 '17 at 22:17
3
I'm not sure when it was added but the command palette now has "Reload Window", which is ideal for this sort of thing.
– Coderer
Aug 7 '17 at 6:46
|
show 5 more comments
Although VS Code is a great editor for TypeScript projects, it needs a kick every now and again. Often, without warning, certain files cause it to freak out and complain. Mostly the fix seems to be to save and close all open files, then open tsconfig.json
. After that you should be able to re-open the offending file without error. If it doesn't work, lather, rinse, and repeat.
If your tsconfig.json
specifies its source files using the files
array, IntelliSense will only function correctly if the file in question is referenced such that VS Code can find it by traversing the input file tree.
Edit: The 'reload window' command (added ages ago now) should solve this problem once and for all.
4
Thank you - removing "files" from tsconfig.json resolve problem
– bensiu
Jul 11 '16 at 14:35
2
The answer was not really relevant to my case but somehow helped my figure out my problem. I am using VS 2015 and between changing thexproj
andtsconfig
file, I missed the fact that the folder with my script files was listed in theexclude
section oftsconfig
. Hope this helps someone.
– Stefan Balan
Sep 3 '16 at 18:10
5
File > Close folder > Open folder worked for me. This happened after I restarted the machine without properly closing vscode.
– Adrian Moisa
Mar 24 '17 at 12:28
2
What if i am not using typescript? Only javascript es6?
– Azarus
Apr 22 '17 at 22:17
3
I'm not sure when it was added but the command palette now has "Reload Window", which is ideal for this sort of thing.
– Coderer
Aug 7 '17 at 6:46
|
show 5 more comments
Although VS Code is a great editor for TypeScript projects, it needs a kick every now and again. Often, without warning, certain files cause it to freak out and complain. Mostly the fix seems to be to save and close all open files, then open tsconfig.json
. After that you should be able to re-open the offending file without error. If it doesn't work, lather, rinse, and repeat.
If your tsconfig.json
specifies its source files using the files
array, IntelliSense will only function correctly if the file in question is referenced such that VS Code can find it by traversing the input file tree.
Edit: The 'reload window' command (added ages ago now) should solve this problem once and for all.
Although VS Code is a great editor for TypeScript projects, it needs a kick every now and again. Often, without warning, certain files cause it to freak out and complain. Mostly the fix seems to be to save and close all open files, then open tsconfig.json
. After that you should be able to re-open the offending file without error. If it doesn't work, lather, rinse, and repeat.
If your tsconfig.json
specifies its source files using the files
array, IntelliSense will only function correctly if the file in question is referenced such that VS Code can find it by traversing the input file tree.
Edit: The 'reload window' command (added ages ago now) should solve this problem once and for all.
edited Nov 25 '18 at 13:21
answered Jul 10 '16 at 21:39
linguamachinalinguamachina
2,05311218
2,05311218
4
Thank you - removing "files" from tsconfig.json resolve problem
– bensiu
Jul 11 '16 at 14:35
2
The answer was not really relevant to my case but somehow helped my figure out my problem. I am using VS 2015 and between changing thexproj
andtsconfig
file, I missed the fact that the folder with my script files was listed in theexclude
section oftsconfig
. Hope this helps someone.
– Stefan Balan
Sep 3 '16 at 18:10
5
File > Close folder > Open folder worked for me. This happened after I restarted the machine without properly closing vscode.
– Adrian Moisa
Mar 24 '17 at 12:28
2
What if i am not using typescript? Only javascript es6?
– Azarus
Apr 22 '17 at 22:17
3
I'm not sure when it was added but the command palette now has "Reload Window", which is ideal for this sort of thing.
– Coderer
Aug 7 '17 at 6:46
|
show 5 more comments
4
Thank you - removing "files" from tsconfig.json resolve problem
– bensiu
Jul 11 '16 at 14:35
2
The answer was not really relevant to my case but somehow helped my figure out my problem. I am using VS 2015 and between changing thexproj
andtsconfig
file, I missed the fact that the folder with my script files was listed in theexclude
section oftsconfig
. Hope this helps someone.
– Stefan Balan
Sep 3 '16 at 18:10
5
File > Close folder > Open folder worked for me. This happened after I restarted the machine without properly closing vscode.
– Adrian Moisa
Mar 24 '17 at 12:28
2
What if i am not using typescript? Only javascript es6?
– Azarus
Apr 22 '17 at 22:17
3
I'm not sure when it was added but the command palette now has "Reload Window", which is ideal for this sort of thing.
– Coderer
Aug 7 '17 at 6:46
4
4
Thank you - removing "files" from tsconfig.json resolve problem
– bensiu
Jul 11 '16 at 14:35
Thank you - removing "files" from tsconfig.json resolve problem
– bensiu
Jul 11 '16 at 14:35
2
2
The answer was not really relevant to my case but somehow helped my figure out my problem. I am using VS 2015 and between changing the
xproj
and tsconfig
file, I missed the fact that the folder with my script files was listed in the exclude
section of tsconfig
. Hope this helps someone.– Stefan Balan
Sep 3 '16 at 18:10
The answer was not really relevant to my case but somehow helped my figure out my problem. I am using VS 2015 and between changing the
xproj
and tsconfig
file, I missed the fact that the folder with my script files was listed in the exclude
section of tsconfig
. Hope this helps someone.– Stefan Balan
Sep 3 '16 at 18:10
5
5
File > Close folder > Open folder worked for me. This happened after I restarted the machine without properly closing vscode.
– Adrian Moisa
Mar 24 '17 at 12:28
File > Close folder > Open folder worked for me. This happened after I restarted the machine without properly closing vscode.
– Adrian Moisa
Mar 24 '17 at 12:28
2
2
What if i am not using typescript? Only javascript es6?
– Azarus
Apr 22 '17 at 22:17
What if i am not using typescript? Only javascript es6?
– Azarus
Apr 22 '17 at 22:17
3
3
I'm not sure when it was added but the command palette now has "Reload Window", which is ideal for this sort of thing.
– Coderer
Aug 7 '17 at 6:46
I'm not sure when it was added but the command palette now has "Reload Window", which is ideal for this sort of thing.
– Coderer
Aug 7 '17 at 6:46
|
show 5 more comments
I've to add the following in the settings.json file of vscode to remove the warning.
"javascript.implicitProjectConfig.experimentalDecorators": true
VSCode -> Preferences -> Settings
Thanks a lot. I'm using es6+decorators and have not typescript installed. Awesome.
– Achmedzianov Danilian
Jan 18 '18 at 11:56
2
This answer is the best, because there's no need to create a separated file in the project to solve a VSCode issue.
– Rodrigo
Mar 14 '18 at 3:22
ctrl + ,
shortcut key to open usersettings. on usersettings click 3 dots (...
) then on pop up clickOpen settings.json
to opensettings.json
– simple_human
Oct 3 '18 at 9:37
add a comment |
I've to add the following in the settings.json file of vscode to remove the warning.
"javascript.implicitProjectConfig.experimentalDecorators": true
VSCode -> Preferences -> Settings
Thanks a lot. I'm using es6+decorators and have not typescript installed. Awesome.
– Achmedzianov Danilian
Jan 18 '18 at 11:56
2
This answer is the best, because there's no need to create a separated file in the project to solve a VSCode issue.
– Rodrigo
Mar 14 '18 at 3:22
ctrl + ,
shortcut key to open usersettings. on usersettings click 3 dots (...
) then on pop up clickOpen settings.json
to opensettings.json
– simple_human
Oct 3 '18 at 9:37
add a comment |
I've to add the following in the settings.json file of vscode to remove the warning.
"javascript.implicitProjectConfig.experimentalDecorators": true
VSCode -> Preferences -> Settings
I've to add the following in the settings.json file of vscode to remove the warning.
"javascript.implicitProjectConfig.experimentalDecorators": true
VSCode -> Preferences -> Settings
answered Jan 10 '18 at 10:50
Manoj PaulManoj Paul
1,4511710
1,4511710
Thanks a lot. I'm using es6+decorators and have not typescript installed. Awesome.
– Achmedzianov Danilian
Jan 18 '18 at 11:56
2
This answer is the best, because there's no need to create a separated file in the project to solve a VSCode issue.
– Rodrigo
Mar 14 '18 at 3:22
ctrl + ,
shortcut key to open usersettings. on usersettings click 3 dots (...
) then on pop up clickOpen settings.json
to opensettings.json
– simple_human
Oct 3 '18 at 9:37
add a comment |
Thanks a lot. I'm using es6+decorators and have not typescript installed. Awesome.
– Achmedzianov Danilian
Jan 18 '18 at 11:56
2
This answer is the best, because there's no need to create a separated file in the project to solve a VSCode issue.
– Rodrigo
Mar 14 '18 at 3:22
ctrl + ,
shortcut key to open usersettings. on usersettings click 3 dots (...
) then on pop up clickOpen settings.json
to opensettings.json
– simple_human
Oct 3 '18 at 9:37
Thanks a lot. I'm using es6+decorators and have not typescript installed. Awesome.
– Achmedzianov Danilian
Jan 18 '18 at 11:56
Thanks a lot. I'm using es6+decorators and have not typescript installed. Awesome.
– Achmedzianov Danilian
Jan 18 '18 at 11:56
2
2
This answer is the best, because there's no need to create a separated file in the project to solve a VSCode issue.
– Rodrigo
Mar 14 '18 at 3:22
This answer is the best, because there's no need to create a separated file in the project to solve a VSCode issue.
– Rodrigo
Mar 14 '18 at 3:22
ctrl + ,
shortcut key to open usersettings. on usersettings click 3 dots (...
) then on pop up click Open settings.json
to open settings.json
– simple_human
Oct 3 '18 at 9:37
ctrl + ,
shortcut key to open usersettings. on usersettings click 3 dots (...
) then on pop up click Open settings.json
to open settings.json
– simple_human
Oct 3 '18 at 9:37
add a comment |
This error also occurs when you choose "src" folder for your workspace folder.
When the root folder, folder where the "src", "node_modules" are located is chosen, the error disappears
5
Came here to post this. This fixed it for me. I was using Angular 2 via Angular CLI.
– async
Jun 30 '17 at 12:17
4
This worked for me on Visual Studio Code. Thanks !
– franpen
Oct 11 '17 at 13:53
add a comment |
This error also occurs when you choose "src" folder for your workspace folder.
When the root folder, folder where the "src", "node_modules" are located is chosen, the error disappears
5
Came here to post this. This fixed it for me. I was using Angular 2 via Angular CLI.
– async
Jun 30 '17 at 12:17
4
This worked for me on Visual Studio Code. Thanks !
– franpen
Oct 11 '17 at 13:53
add a comment |
This error also occurs when you choose "src" folder for your workspace folder.
When the root folder, folder where the "src", "node_modules" are located is chosen, the error disappears
This error also occurs when you choose "src" folder for your workspace folder.
When the root folder, folder where the "src", "node_modules" are located is chosen, the error disappears
answered May 5 '17 at 0:08
Semir DeljićSemir Deljić
1,3471816
1,3471816
5
Came here to post this. This fixed it for me. I was using Angular 2 via Angular CLI.
– async
Jun 30 '17 at 12:17
4
This worked for me on Visual Studio Code. Thanks !
– franpen
Oct 11 '17 at 13:53
add a comment |
5
Came here to post this. This fixed it for me. I was using Angular 2 via Angular CLI.
– async
Jun 30 '17 at 12:17
4
This worked for me on Visual Studio Code. Thanks !
– franpen
Oct 11 '17 at 13:53
5
5
Came here to post this. This fixed it for me. I was using Angular 2 via Angular CLI.
– async
Jun 30 '17 at 12:17
Came here to post this. This fixed it for me. I was using Angular 2 via Angular CLI.
– async
Jun 30 '17 at 12:17
4
4
This worked for me on Visual Studio Code. Thanks !
– franpen
Oct 11 '17 at 13:53
This worked for me on Visual Studio Code. Thanks !
– franpen
Oct 11 '17 at 13:53
add a comment |
have to add typescript.tsdk
to my .vscode/settings.json
:
"typescript.tsdk": "node_modules/typescript/lib"
4
This solved the issue for me, but that line goes into.vscode/settings.json
as per this
– Fran Rodriguez
Sep 20 '16 at 16:42
1
Also solved it for me, but I didn't have the.vscode
folder (I don't know why - I'm a backend dev, leave me alone!), so I created one in the root folder with saidsettings.json
file.
– cr4ne
May 10 '17 at 6:13
add a comment |
have to add typescript.tsdk
to my .vscode/settings.json
:
"typescript.tsdk": "node_modules/typescript/lib"
4
This solved the issue for me, but that line goes into.vscode/settings.json
as per this
– Fran Rodriguez
Sep 20 '16 at 16:42
1
Also solved it for me, but I didn't have the.vscode
folder (I don't know why - I'm a backend dev, leave me alone!), so I created one in the root folder with saidsettings.json
file.
– cr4ne
May 10 '17 at 6:13
add a comment |
have to add typescript.tsdk
to my .vscode/settings.json
:
"typescript.tsdk": "node_modules/typescript/lib"
have to add typescript.tsdk
to my .vscode/settings.json
:
"typescript.tsdk": "node_modules/typescript/lib"
edited Jan 22 '17 at 21:24
David Cheung
2,56232548
2,56232548
answered Sep 19 '16 at 8:59
beewestbeewest
1,21121029
1,21121029
4
This solved the issue for me, but that line goes into.vscode/settings.json
as per this
– Fran Rodriguez
Sep 20 '16 at 16:42
1
Also solved it for me, but I didn't have the.vscode
folder (I don't know why - I'm a backend dev, leave me alone!), so I created one in the root folder with saidsettings.json
file.
– cr4ne
May 10 '17 at 6:13
add a comment |
4
This solved the issue for me, but that line goes into.vscode/settings.json
as per this
– Fran Rodriguez
Sep 20 '16 at 16:42
1
Also solved it for me, but I didn't have the.vscode
folder (I don't know why - I'm a backend dev, leave me alone!), so I created one in the root folder with saidsettings.json
file.
– cr4ne
May 10 '17 at 6:13
4
4
This solved the issue for me, but that line goes into
.vscode/settings.json
as per this– Fran Rodriguez
Sep 20 '16 at 16:42
This solved the issue for me, but that line goes into
.vscode/settings.json
as per this– Fran Rodriguez
Sep 20 '16 at 16:42
1
1
Also solved it for me, but I didn't have the
.vscode
folder (I don't know why - I'm a backend dev, leave me alone!), so I created one in the root folder with said settings.json
file.– cr4ne
May 10 '17 at 6:13
Also solved it for me, but I didn't have the
.vscode
folder (I don't know why - I'm a backend dev, leave me alone!), so I created one in the root folder with said settings.json
file.– cr4ne
May 10 '17 at 6:13
add a comment |
inside your project create file tsconfig.json , then add this lines
{
"compilerOptions": {
"experimentalDecorators": true,
"allowJs": true
}
}
add a comment |
inside your project create file tsconfig.json , then add this lines
{
"compilerOptions": {
"experimentalDecorators": true,
"allowJs": true
}
}
add a comment |
inside your project create file tsconfig.json , then add this lines
{
"compilerOptions": {
"experimentalDecorators": true,
"allowJs": true
}
}
inside your project create file tsconfig.json , then add this lines
{
"compilerOptions": {
"experimentalDecorators": true,
"allowJs": true
}
}
answered Jul 10 '17 at 12:01
Muhammed MoussaMuhammed Moussa
22325
22325
add a comment |
add a comment |
"javascript.implicitProjectConfig.experimentalDecorators": true
Will solve this problem.
add a comment |
"javascript.implicitProjectConfig.experimentalDecorators": true
Will solve this problem.
add a comment |
"javascript.implicitProjectConfig.experimentalDecorators": true
Will solve this problem.
"javascript.implicitProjectConfig.experimentalDecorators": true
Will solve this problem.
edited May 6 '18 at 13:24
eyllanesc
80.3k103258
80.3k103258
answered May 6 '18 at 12:42
Rajesh PalRajesh Pal
9113
9113
add a comment |
add a comment |
Open settings.json
file in the following location <project_folder>/.vscode/settings.json
or you can open the file from the menu as mentioned below
VSCode -> File -> Preferences -> Workspace Settings
Then add the following lines in settings.json
file
{
"typescript.tsdk": "node_modules/typescript/lib",
"enable_typescript_language_service": false
}
That's all. You will see no warning/error regarding 'experimentalDecorators'
10
I got "Unknown configuration setting" after adding "enable_typescript_language_service" using vscode 1.8.1
– David Cheung
Jan 22 '17 at 12:35
2
This is HORRIBLE advice if your project uses Typescript!
– paulsm4
Jan 3 at 17:22
add a comment |
Open settings.json
file in the following location <project_folder>/.vscode/settings.json
or you can open the file from the menu as mentioned below
VSCode -> File -> Preferences -> Workspace Settings
Then add the following lines in settings.json
file
{
"typescript.tsdk": "node_modules/typescript/lib",
"enable_typescript_language_service": false
}
That's all. You will see no warning/error regarding 'experimentalDecorators'
10
I got "Unknown configuration setting" after adding "enable_typescript_language_service" using vscode 1.8.1
– David Cheung
Jan 22 '17 at 12:35
2
This is HORRIBLE advice if your project uses Typescript!
– paulsm4
Jan 3 at 17:22
add a comment |
Open settings.json
file in the following location <project_folder>/.vscode/settings.json
or you can open the file from the menu as mentioned below
VSCode -> File -> Preferences -> Workspace Settings
Then add the following lines in settings.json
file
{
"typescript.tsdk": "node_modules/typescript/lib",
"enable_typescript_language_service": false
}
That's all. You will see no warning/error regarding 'experimentalDecorators'
Open settings.json
file in the following location <project_folder>/.vscode/settings.json
or you can open the file from the menu as mentioned below
VSCode -> File -> Preferences -> Workspace Settings
Then add the following lines in settings.json
file
{
"typescript.tsdk": "node_modules/typescript/lib",
"enable_typescript_language_service": false
}
That's all. You will see no warning/error regarding 'experimentalDecorators'
edited Oct 27 '16 at 12:41
answered Oct 27 '16 at 12:23
Vinothkumar ArputharajVinothkumar Arputharaj
3,72742332
3,72742332
10
I got "Unknown configuration setting" after adding "enable_typescript_language_service" using vscode 1.8.1
– David Cheung
Jan 22 '17 at 12:35
2
This is HORRIBLE advice if your project uses Typescript!
– paulsm4
Jan 3 at 17:22
add a comment |
10
I got "Unknown configuration setting" after adding "enable_typescript_language_service" using vscode 1.8.1
– David Cheung
Jan 22 '17 at 12:35
2
This is HORRIBLE advice if your project uses Typescript!
– paulsm4
Jan 3 at 17:22
10
10
I got "Unknown configuration setting" after adding "enable_typescript_language_service" using vscode 1.8.1
– David Cheung
Jan 22 '17 at 12:35
I got "Unknown configuration setting" after adding "enable_typescript_language_service" using vscode 1.8.1
– David Cheung
Jan 22 '17 at 12:35
2
2
This is HORRIBLE advice if your project uses Typescript!
– paulsm4
Jan 3 at 17:22
This is HORRIBLE advice if your project uses Typescript!
– paulsm4
Jan 3 at 17:22
add a comment |
This answer is intended for people who are using a Javascript project and not a Typescript one. Instead of a tsconfig.json file you may use a jsconfig.json file.
In the particular case of having the decorators warning you wan write inside the file:
{
"compilerOptions": {
"experimentalDecorators": true
}
}
Fort the buggy behaviors asked, it's always better to specify the "include" in the config file, and restart the editor. E.g.
{
"compilerOptions": {
"target": "ES6",
"experimentalDecorators": true
},
"include": [
"app/**/*"
],
"exclude": [
"node_modules"
]
}
add a comment |
This answer is intended for people who are using a Javascript project and not a Typescript one. Instead of a tsconfig.json file you may use a jsconfig.json file.
In the particular case of having the decorators warning you wan write inside the file:
{
"compilerOptions": {
"experimentalDecorators": true
}
}
Fort the buggy behaviors asked, it's always better to specify the "include" in the config file, and restart the editor. E.g.
{
"compilerOptions": {
"target": "ES6",
"experimentalDecorators": true
},
"include": [
"app/**/*"
],
"exclude": [
"node_modules"
]
}
add a comment |
This answer is intended for people who are using a Javascript project and not a Typescript one. Instead of a tsconfig.json file you may use a jsconfig.json file.
In the particular case of having the decorators warning you wan write inside the file:
{
"compilerOptions": {
"experimentalDecorators": true
}
}
Fort the buggy behaviors asked, it's always better to specify the "include" in the config file, and restart the editor. E.g.
{
"compilerOptions": {
"target": "ES6",
"experimentalDecorators": true
},
"include": [
"app/**/*"
],
"exclude": [
"node_modules"
]
}
This answer is intended for people who are using a Javascript project and not a Typescript one. Instead of a tsconfig.json file you may use a jsconfig.json file.
In the particular case of having the decorators warning you wan write inside the file:
{
"compilerOptions": {
"experimentalDecorators": true
}
}
Fort the buggy behaviors asked, it's always better to specify the "include" in the config file, and restart the editor. E.g.
{
"compilerOptions": {
"target": "ES6",
"experimentalDecorators": true
},
"include": [
"app/**/*"
],
"exclude": [
"node_modules"
]
}
edited Jun 15 '17 at 15:50
answered Jun 15 '17 at 15:44
Pere PagesPere Pages
4,52911925
4,52911925
add a comment |
add a comment |
Add following lines in tsconfig.json and restart VS Code.
{
"compilerOptions": {
"experimentalDecorators": true,
"target": "es5",
"allowJs": true
}
}
The restart was the key for me. Thanks.
– rynop
Jan 10 at 5:34
add a comment |
Add following lines in tsconfig.json and restart VS Code.
{
"compilerOptions": {
"experimentalDecorators": true,
"target": "es5",
"allowJs": true
}
}
The restart was the key for me. Thanks.
– rynop
Jan 10 at 5:34
add a comment |
Add following lines in tsconfig.json and restart VS Code.
{
"compilerOptions": {
"experimentalDecorators": true,
"target": "es5",
"allowJs": true
}
}
Add following lines in tsconfig.json and restart VS Code.
{
"compilerOptions": {
"experimentalDecorators": true,
"target": "es5",
"allowJs": true
}
}
edited Feb 24 '18 at 8:29
hofmeister
1,91983561
1,91983561
answered Feb 24 '18 at 6:38
GeeteshGeetesh
13417
13417
The restart was the key for me. Thanks.
– rynop
Jan 10 at 5:34
add a comment |
The restart was the key for me. Thanks.
– rynop
Jan 10 at 5:34
The restart was the key for me. Thanks.
– rynop
Jan 10 at 5:34
The restart was the key for me. Thanks.
– rynop
Jan 10 at 5:34
add a comment |
Not to belabor the point but be sure to add the following to
- Workspace Settings not User Settings
under File >> Preferences >> Settings
"javascript.implicitProjectConfig.experimentalDecorators": true
this fixed the issue for me, and i tried quite a few suggestions i found here and other places.
add a comment |
Not to belabor the point but be sure to add the following to
- Workspace Settings not User Settings
under File >> Preferences >> Settings
"javascript.implicitProjectConfig.experimentalDecorators": true
this fixed the issue for me, and i tried quite a few suggestions i found here and other places.
add a comment |
Not to belabor the point but be sure to add the following to
- Workspace Settings not User Settings
under File >> Preferences >> Settings
"javascript.implicitProjectConfig.experimentalDecorators": true
this fixed the issue for me, and i tried quite a few suggestions i found here and other places.
Not to belabor the point but be sure to add the following to
- Workspace Settings not User Settings
under File >> Preferences >> Settings
"javascript.implicitProjectConfig.experimentalDecorators": true
this fixed the issue for me, and i tried quite a few suggestions i found here and other places.
answered Jun 6 '18 at 12:52
petey mpetey m
78210
78210
add a comment |
add a comment |
For the sake of clarity and stupidity.
1) Open .vscode/settings.json.
2) Add "typescript.tsdk": "node_modules/typescript/lib" on it.
3) Save it.
4) Restart Visual Studio Code.
add a comment |
For the sake of clarity and stupidity.
1) Open .vscode/settings.json.
2) Add "typescript.tsdk": "node_modules/typescript/lib" on it.
3) Save it.
4) Restart Visual Studio Code.
add a comment |
For the sake of clarity and stupidity.
1) Open .vscode/settings.json.
2) Add "typescript.tsdk": "node_modules/typescript/lib" on it.
3) Save it.
4) Restart Visual Studio Code.
For the sake of clarity and stupidity.
1) Open .vscode/settings.json.
2) Add "typescript.tsdk": "node_modules/typescript/lib" on it.
3) Save it.
4) Restart Visual Studio Code.
answered Jan 9 '17 at 12:19
LEMUEL ADANELEMUEL ADANE
2,451103259
2,451103259
add a comment |
add a comment |
Please check you oppened in your VS Code the folder of the entire project and not only the src folder, because if you open only the src, then ts.config.json (located in the project folder) file will not be in scope, and VS will not recognize the experimental decorators parameters.
In my case this fixed all the problems related to this issue.
This was also my issue. Can you see node_modules? Can you see tsconfig.json? If not, open a new vsCode window, close the old window, choose file-->open folder, and make sure you select the parent folder ofsrc
andnode_modules
, rather than selecting justsrc
.
– Kyle Vassella
Feb 13 at 23:40
add a comment |
Please check you oppened in your VS Code the folder of the entire project and not only the src folder, because if you open only the src, then ts.config.json (located in the project folder) file will not be in scope, and VS will not recognize the experimental decorators parameters.
In my case this fixed all the problems related to this issue.
This was also my issue. Can you see node_modules? Can you see tsconfig.json? If not, open a new vsCode window, close the old window, choose file-->open folder, and make sure you select the parent folder ofsrc
andnode_modules
, rather than selecting justsrc
.
– Kyle Vassella
Feb 13 at 23:40
add a comment |
Please check you oppened in your VS Code the folder of the entire project and not only the src folder, because if you open only the src, then ts.config.json (located in the project folder) file will not be in scope, and VS will not recognize the experimental decorators parameters.
In my case this fixed all the problems related to this issue.
Please check you oppened in your VS Code the folder of the entire project and not only the src folder, because if you open only the src, then ts.config.json (located in the project folder) file will not be in scope, and VS will not recognize the experimental decorators parameters.
In my case this fixed all the problems related to this issue.
answered Aug 17 '18 at 2:16
dayanrr91dayanrr91
95111
95111
This was also my issue. Can you see node_modules? Can you see tsconfig.json? If not, open a new vsCode window, close the old window, choose file-->open folder, and make sure you select the parent folder ofsrc
andnode_modules
, rather than selecting justsrc
.
– Kyle Vassella
Feb 13 at 23:40
add a comment |
This was also my issue. Can you see node_modules? Can you see tsconfig.json? If not, open a new vsCode window, close the old window, choose file-->open folder, and make sure you select the parent folder ofsrc
andnode_modules
, rather than selecting justsrc
.
– Kyle Vassella
Feb 13 at 23:40
This was also my issue. Can you see node_modules? Can you see tsconfig.json? If not, open a new vsCode window, close the old window, choose file-->open folder, and make sure you select the parent folder of
src
and node_modules
, rather than selecting just src
.– Kyle Vassella
Feb 13 at 23:40
This was also my issue. Can you see node_modules? Can you see tsconfig.json? If not, open a new vsCode window, close the old window, choose file-->open folder, and make sure you select the parent folder of
src
and node_modules
, rather than selecting just src
.– Kyle Vassella
Feb 13 at 23:40
add a comment |
If you are working in Visual studio. You can try this fix
- Unload your project from visual studio
- Go to your project home directory and Open "csproj" file.
Add TypeScriptExperimentalDecorators to this section as shown in image
- Reload the project in Visual studio.
see more details at this location.
add a comment |
If you are working in Visual studio. You can try this fix
- Unload your project from visual studio
- Go to your project home directory and Open "csproj" file.
Add TypeScriptExperimentalDecorators to this section as shown in image
- Reload the project in Visual studio.
see more details at this location.
add a comment |
If you are working in Visual studio. You can try this fix
- Unload your project from visual studio
- Go to your project home directory and Open "csproj" file.
Add TypeScriptExperimentalDecorators to this section as shown in image
- Reload the project in Visual studio.
see more details at this location.
If you are working in Visual studio. You can try this fix
- Unload your project from visual studio
- Go to your project home directory and Open "csproj" file.
Add TypeScriptExperimentalDecorators to this section as shown in image
- Reload the project in Visual studio.
see more details at this location.
answered Jan 2 '18 at 14:42
kumar chandraketukumar chandraketu
9061616
9061616
add a comment |
add a comment |
I corrected the warning by removing "baseUrl": "", from the tsconfig.json file
add a comment |
I corrected the warning by removing "baseUrl": "", from the tsconfig.json file
add a comment |
I corrected the warning by removing "baseUrl": "", from the tsconfig.json file
I corrected the warning by removing "baseUrl": "", from the tsconfig.json file
answered Jan 24 '17 at 0:08
D. GreeneD. Greene
443
443
add a comment |
add a comment |
Open entire project's folder instead of project-name/src
tsconfig.json is out of src folder
add a comment |
Open entire project's folder instead of project-name/src
tsconfig.json is out of src folder
add a comment |
Open entire project's folder instead of project-name/src
tsconfig.json is out of src folder
Open entire project's folder instead of project-name/src
tsconfig.json is out of src folder
answered Oct 18 '17 at 20:02
Andrew YavorskyAndrew Yavorsky
192
192
add a comment |
add a comment |
- Open VScode.
- Press ctrl+comma
- Follow the directions in the screen shot
- Search about
experimentalDecorators - Edit it
- Search about
add a comment |
- Open VScode.
- Press ctrl+comma
- Follow the directions in the screen shot
- Search about
experimentalDecorators - Edit it
- Search about
add a comment |
- Open VScode.
- Press ctrl+comma
- Follow the directions in the screen shot
- Search about
experimentalDecorators - Edit it
- Search about
- Open VScode.
- Press ctrl+comma
- Follow the directions in the screen shot
- Search about
experimentalDecorators - Edit it
- Search about
edited Jan 9 '18 at 13:00
Spangen
1,89031824
1,89031824
answered Jan 9 '18 at 12:47
MostafaMostafa
113
113
add a comment |
add a comment |
I had this problem recently under Visual Studio 2017 - turned out it was caused by a "feature" of VS - ignoring tsconfig.json when Build action is not set to Content.
So changing the Build action to Content and reloading the solution solved the problem.
add a comment |
I had this problem recently under Visual Studio 2017 - turned out it was caused by a "feature" of VS - ignoring tsconfig.json when Build action is not set to Content.
So changing the Build action to Content and reloading the solution solved the problem.
add a comment |
I had this problem recently under Visual Studio 2017 - turned out it was caused by a "feature" of VS - ignoring tsconfig.json when Build action is not set to Content.
So changing the Build action to Content and reloading the solution solved the problem.
I had this problem recently under Visual Studio 2017 - turned out it was caused by a "feature" of VS - ignoring tsconfig.json when Build action is not set to Content.
So changing the Build action to Content and reloading the solution solved the problem.
answered Aug 17 '18 at 11:40
Pawel GorczynskiPawel Gorczynski
51948
51948
add a comment |
add a comment |
You might run into this issue if you open a TS file that exists outside of the project. For instance, I'm using lerna and had a file open from another package. Although that other package had it's own tsconfig with experimental decorators, VsCode doesn't honor it.
add a comment |
You might run into this issue if you open a TS file that exists outside of the project. For instance, I'm using lerna and had a file open from another package. Although that other package had it's own tsconfig with experimental decorators, VsCode doesn't honor it.
add a comment |
You might run into this issue if you open a TS file that exists outside of the project. For instance, I'm using lerna and had a file open from another package. Although that other package had it's own tsconfig with experimental decorators, VsCode doesn't honor it.
You might run into this issue if you open a TS file that exists outside of the project. For instance, I'm using lerna and had a file open from another package. Although that other package had it's own tsconfig with experimental decorators, VsCode doesn't honor it.
answered Nov 7 '17 at 20:18
sparebytessparebytes
7,31921224
7,31921224
add a comment |
add a comment |
I faced the same issue while creating an Injectable Services in Angular 2.
I have all the things at place in tsconfig.json .Still I was getting this error at ColorsImmutable line.
@Injectable()
export class ColorsImmutable {
And fix was to register the Service at module Level or Component Level
using the providers array.
providers:[ColorsImmutable ],
add a comment |
I faced the same issue while creating an Injectable Services in Angular 2.
I have all the things at place in tsconfig.json .Still I was getting this error at ColorsImmutable line.
@Injectable()
export class ColorsImmutable {
And fix was to register the Service at module Level or Component Level
using the providers array.
providers:[ColorsImmutable ],
add a comment |
I faced the same issue while creating an Injectable Services in Angular 2.
I have all the things at place in tsconfig.json .Still I was getting this error at ColorsImmutable line.
@Injectable()
export class ColorsImmutable {
And fix was to register the Service at module Level or Component Level
using the providers array.
providers:[ColorsImmutable ],
I faced the same issue while creating an Injectable Services in Angular 2.
I have all the things at place in tsconfig.json .Still I was getting this error at ColorsImmutable line.
@Injectable()
export class ColorsImmutable {
And fix was to register the Service at module Level or Component Level
using the providers array.
providers:[ColorsImmutable ],
answered Nov 9 '17 at 10:27
Mohammad JavedMohammad Javed
497
497
add a comment |
add a comment |
I added this option to tsconfig.json, "baseUrl": "front-end"
Replace front-end with the name of your angular-cli project.
add a comment |
I added this option to tsconfig.json, "baseUrl": "front-end"
Replace front-end with the name of your angular-cli project.
add a comment |
I added this option to tsconfig.json, "baseUrl": "front-end"
Replace front-end with the name of your angular-cli project.
I added this option to tsconfig.json, "baseUrl": "front-end"
Replace front-end with the name of your angular-cli project.
answered Jan 14 '18 at 20:46
Sean MaxwellSean Maxwell
111
111
add a comment |
add a comment |
If you are using cli to compile *.ts files, you can set experimentalDecorators using the following command:
tsc filename.ts --experimentalDecorators "true"
add a comment |
If you are using cli to compile *.ts files, you can set experimentalDecorators using the following command:
tsc filename.ts --experimentalDecorators "true"
add a comment |
If you are using cli to compile *.ts files, you can set experimentalDecorators using the following command:
tsc filename.ts --experimentalDecorators "true"
If you are using cli to compile *.ts files, you can set experimentalDecorators using the following command:
tsc filename.ts --experimentalDecorators "true"
answered Jul 6 '18 at 21:16
Akoji EIAkoji EI
559412
559412
add a comment |
add a comment |
protected by eyllanesc May 6 '18 at 13:25
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
3
Have you tried restarting VS Code? I've found that's necessary after making tsconfig.json changes sometimes.
– David Sherret
Jul 8 '16 at 16:26
Yes - I did it a few times - only difference is that different file is not having warning but others still
– bensiu
Jul 8 '16 at 16:38
2
You can try blow answer dude. It work for me! stackoverflow.com/a/38970591/2468781
– erdemildiz
May 10 '17 at 18:20
3
By chance if someone else runs into this that is using VS Professional, not VS Code, you may have added a
.ts
file to an angular project manually; if so, the default TS compilation is conflicting with Angular CLI. Right-click the file -> Properties -> Build Action : None. Then restart VS if needed.– pbarranis
Jul 19 '18 at 14:16
VS Code restart helped me solve the issue.
– CMA
Nov 6 '18 at 6:28