Errors arose due to the deployment of TypeScript decorators

Question

Errors arose due to the deployment of TypeScript decorators

Using TypeScript in a brand new ASP.NET Core project has brought some challenges.

We are actively incorporating decorators into our codebase.

However, this integration is causing numerous errors to appear in the output of VS2015:

Error   TS1219  Experimental support for decorators is a feature that is subject to change in a future release.
Specify '--experimentalDecorators' to remove this warning.  
WebApplication2 d:\documents\visual studio 2015\Projects\WebApplication2\src\WebApplication2\wwwroot\sources\app.ts 9   Active

There are solutions available for removing these error messages when working with regular ASP.NET projects by modifying the *.csproj file.

However, ASP.NET Core projects utilize the .xproj file structure instead.

So, how can we enable experimental TypeScript decorator support in VS2015 for an ASP.NET Core project?

You can access a simple project showcasing this issue on a sample github repository

typescript visual-studio-2015 asp.net-core

Answer 1

Answer №1

To get started, right click on your project and select Add then choose New Item.
From the menu on the left, choose Client-side.
Now, add a new file called
```
TypeScript JSON Configuration File
```
with the default name of tsconfig.json.
Next, open up the tsconfig.json file, locate the complierOptions section, and include "experimentalDecorators": true.
Don't forget to remove "wwwroot" from the "exclude" section.
Once you've made these changes, build your project and enjoy!

For reference, here is the content of my tsconfig.json file:

{
  "compilerOptions": {
    "noImplicitAny": false,
    "noEmitOnError": true,
    "removeComments": false,
    "sourceMap": true,
    "target": "es5",
    "experimentalDecorators": true
  },
  "exclude": [
    "node_modules"
  ]
}

Answer 2

To get started, right click on your project and select Add then choose New Item.
From the menu on the left, choose Client-side.
Now, add a new file called
```
TypeScript JSON Configuration File
```
with the default name of tsconfig.json.
Next, open up the tsconfig.json file, locate the complierOptions section, and include "experimentalDecorators": true.
Don't forget to remove "wwwroot" from the "exclude" section.
Once you've made these changes, build your project and enjoy!

For reference, here is the content of my tsconfig.json file:

{
  "compilerOptions": {
    "noImplicitAny": false,
    "noEmitOnError": true,
    "removeComments": false,
    "sourceMap": true,
    "target": "es5",
    "experimentalDecorators": true
  },
  "exclude": [
    "node_modules"
  ]
}

Errors arose due to the deployment of TypeScript decorators

Answer №1

Similar questions

Intermittent issue with Angular 2 encountered while following the Hero Editor tutorial on angular.io

Changing the Class of an Element in a Different Component with Angular 2+

Creating a specialized feature for saving form data with React Admin

Is Angular UI's data binding more of a push or pull mechanism? How can I optimize its speed?

What is the reason behind decorators needing to utilize apply(this) on a function?

What happens when i18next's fallbackLng takes precedence over changeLanguage?

Create a system for detecting changes in simple input elements and triggering a function to update the final result

Tips for integrating Tesseract with Angular 2 and above

You can only use a parameter initializer within the implementation of a function or constructor

Is your TypeScript spread functionality not functioning as expected?

What is the best way to retrieve a function's response depending on the parameters provided?

Retrieve a specific attribute from a collection of JSON objects and transfer it to a separate object

Simple methods for ensuring a minimum time interval between observable emittance

Click to alter the style of an <li> element

What are the steps to effectively implement the useEffect hook in React?

Issue encountered while accessing theme properties in a ReactJs component with Typescript

Controller does not have a mapping to API Uri

Is it possible in TypeScript to change a string literal type into a number type?

Unit testing of an expired JWT token fails due to the incorrect setting of the "options.expiresIn" parameter, as the payload already contains an "exp" property

Error: The variable "document" is not defined in the context of NextJS TypeScript