JSPM

  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • 0
  • Score
    100M100P100Q40407F
  • License MIT

TypeScript language service plugin to let more plugins work in Visual Studio.

Package Exports

  • vs-compat-ts-plugin

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (vs-compat-ts-plugin) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

vs-compat-ts-plugin

Node version Known Vulnerabilities Build Dependencies Dev Dependencies

TypeScript language service plugin to let more plugins work in Visual Studio.

Many language service plugins work perfectly in VS Code, but using them in Visual Studio will break due to various niggles. Ideally these would all be fixed by the plugin maintainers but this plugin can be used as a temporary measure until then.

Installation

npm install --save-dev vs-compat-ts-plugin

Enable the plugin in your tsconfig.json file

{
  "compilerOptions": {
    "plugins": [
      {
        "name": "vs-compat-ts-plugin",
        "workingDirectory": "."
      },
      { "name": "other-plugin" },
      ...
    ]
  }
}

Always make sure this is the first plugin in the list, as it effects how other plugins will be loaded.

You will likely need to restart Visual Studio for any of these settings to take effect

Configuration

workingDirectory (string - default null)

This can set the working directory for the rest of the plugins. In many editors this seems to default to the workspace, but in Visual Studio it tends to be System32.

Relative to the tsconfig. Null means do not set a working directory.

License

MIT