Getting an error for experimental support for decorators with experimentalDecorators enabled

[bartzy]

Hi,

I have enabled the experimentalDecorators option in my tsconfig.json file, but the Sublime Typescript plugin keeps complaining in decorators:

Experimental support for decorators is a feature that is subject to change in a future release. Set the 'experimentalDecorators' option to remove this warning.

Thanks!

[mhegazy]

Can you share your tsconfig.json?

[bartzy]

Sure:

{
    "compilerOptions": {
        "module": "es6",
        "moduleResolution": "node",
        "target": "es6",
        "sourceMap": true,
        "noImplicitAny": true,
        "removeComments": false,
        "experimentalDecorators": true
    },
    "files": [
        "./src/App.ts",
        "./typings/main.d.ts"
    ]
}

[billti]

Are you getting the error for a decorator in one of the 2 files listed in your 'files' property? I you have any additional files open with decorators they may give this error, as they are not included in the above tsconfig.json project (and will thus create their own context).

[bartzy]

@billti Oops. I always forget that. Typescript should really have an include directive in tsconfig.json :)

Thanks!

[Deviad]

Still having this error in Sublime Text 3

tsconfig.json

{
  "compilerOptions": {
    "declaration": false,
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "lib": ["es6", "dom"],
    "mapRoot": "./",
    "module": "es6",
    "moduleResolution": "node",
    "outDir": "../dist/out-tsc",
    "sourceMap": true,
    "target": "es5",
    "typeRoots": [
      "../node_modules/@types"
    ],
    "types": [
      "jasmine"
    ]
  }
}

The project has been generateed with ng-cli.

[gimmeshelter]

@Deviad I am getting this too—same setup.

[victormejia]

@Deviad @gimmeshelter just curious, are you getting this error with the angular-cli webpack version? I'm getting the same errors.

[sorakthun]

@Deviad Same here. I also cannot use module.id. It cannot find name 'module'. I couldn't find solution anywhere.

[radoslavpetranov]

same here - I have an old Angular2 project that I've created manually from scratch and I have no issues. Another project generated with ng-cli a day ago has the sublime issue as well.

[gimmeshelter]

I think I found the solution for this. Set 'typescript_tsdk' to the location of your global typescript node_module in the 'Settings - User' (i.e. Packages/User/Preferences.sublime-settings) file. #493

e.g. "typescript_tsdk": "/usr/local/lib/node_modules/typescript/lib"

[radoslavpetranov]

^^ awesome - thanks heaps @gimmeshelter !! That worked for me!

[radoslavpetranov]

@gimmeshelter out of sheer curiosity - do you know why it was working fine with my old and manually created Angular2 project but it broke when I used Angular CLI to generate the new one? Does the plugin default to a local path that doesn't get updated for new projects or something?

[gimmeshelter]

@radoslavpetranov Great!! Glad it worked! As to your questions: 1) I do not know what changed. I just started with ng-cli and the problem was present from the outset for me. 2) I am not 100% clear, but I think issue #499 might help you understand how the plug-in decides which typescript module to use.