Microsoft/TypeScript-Sublime-Plugin

IO wrapper around TypeScript language services, allowing for easy consumption by editor plugins

Andrew Faulkner

@andfaulkner

Is there any way to get Sublime to recognize import paths relative to a project root rather than relative to the current file?

I've been able to get this behaviour working on compilation (with Webpack, and Typescript 2.0.2), but Sublime is still giving me "Cannot find module" errors.

Andrew Faulkner

@andfaulkner

For example:
I can import component 'fetchRecord' that I've declared in (and exported from): [project_root]/client/redux/reducers/fetchContent.ts
...into this file: [project_root]/client/components/RecordLoaderSidebar/RecordLoaderSidebar.tsx
...using this syntax:
import { fetchRecord } from 'redux/reducers/fetchContent';

It compiles without a problem, but Typescript-Sublime complains, and outputs:
Cannot find module 'redux/reducers/fetchContent'.

rex

@retwedt

I am running into the same issue as @gregbown .

rex

@retwedt

tsconfig.json appears to be set correctly. Running tsc locally does not throw any errors, and my project builds successfully. However, Sublime is giving me feedback that support for Decorators is experimental, and to set the flag in my tsconfig. It is also telling me that vendor modules cannot be resolved.

My tsconfig file:

{
  "compilerOptions": {
    "target": "es5",
    "module": "system",
    "moduleResolution": "node",
    "sourceMap": true,
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "removeComments": false,
    "baseUrl": ".",
    "lib": [
      "es5",
      "es6"
    ],
    "paths": {
      "*": [
        "jspm_packages/npm/*",
        "jspm_packages/github/*",
        "jspm_packages/bitbucket/*"
      ]
    }
  },
  "include": [
    "../app/**/*.ts"
  ]
}

I am using Typescript 2.0.0, JSPM 0.17 Beta, and Sublime Text 3. Any help would be appreciated.

Chris LeBlanc

@spacesuitdiver

Hi, how do i disable the "tooltip" here? http://d.pr/i/UGiz

I wonder if the styling is wrong and it should "float"

Problem is it moves the line down which is super annoying

Bnaya Peretz

@Bnaya

looks like the plugin is ignoring the tsconfig.compilerOptions.lib[]

even when setting the path of the tsserver to ts 2.1.4

bf0

@bf0

So I'm seeing something strange with this plugin where it's giving error messages for previous versions of a file. Does anyone know how this can happen? Is there some caching involved?

Have code with error:
```
this.dialog.open(someDialogComponent, {});
```
--> gives error (correctly) "Argument of type {} is not assignable to paramater of type 'MdDialogConfig ..."
Fix code:
```
this.dialog.open(someDialogComponent);
```
--> still get the same error (incorrectly) "Argument of type {} is not assignable to paramater of type 'MdDialogConfig ..."

... I did have 2 copies of the same project open (from different directories). closed one and it went away. Perhaps that is the bug.

Sergei Vorobev

@vors

Hi guys, what's up with Microsoft/TypeScript-Sublime-Plugin#529 ? This issue is super-duper annoying

I'd be happy to help out, if somebody can point me in the right direction

I searched for "find" and "select" but there is just too much stuff

Daniel Rosenwasser

@DanielRosenwasser

@vors sorry we missed that

@zhengbli will try checking it out when he gets the chance

Sergei Vorobev

@vors

@DanielRosenwasser great! thank you for the quick reply

Let me know if you need help

Daniel Rosenwasser

@DanielRosenwasser

Sure thing!

2010abinas

@2010abinas

Hello all

its showing fatal: Too many arguments.

Anyone please assist me in this issue

i am facing an issue while installing typescript in sublime

Ch1ll0ut1

@ch1ll0ut1

I have code that runs successful through the compiler but sublime shows errors in the ui.
1) import * as assert from 'assert'; # can not find module assert
2) new Promise((resolve, reject) => { # 'Promise' only refers to a type, but is used as a value

Daniel Rosenwasser

@DanielRosenwasser

@ch1ll0ut1 usually that means your file isn't associated with a tsconig.json

James Elkins

@jameselkins

hey all - I'm also running into Microsoft/TypeScript-Sublime-Plugin#529

any idea what might be the problem? @DanielRosenwasser you said @zhengbli might have a chance to look into it :)

I'm on sublime 3136 MacOS 10.12.5

dontwork

@dontwork

hi i am trying to setup baseURL so i dont need to do imports with '../../' but I am still getting squigglies in sublime even though everything is compiling correctly

Diego Benjamín

@daguilaraguilar_twitter

Hello, I installed the package in my Sublime 3 build 3143 install and I got syntax highlighting, however I cant see any actual linting or error alerts

neight signature definitions

Daniel Rosenwasser

@DanielRosenwasser

@daguilaraguilar_twitter Do you have Node installed on your system?

Abdulrhman Alsri

@msman

i installed the typescript but not working!

sublime

Sarthak Batra

@batraman

Hey people! I was going through the release notes of the new version of the plugin with improved syntax highlighting for TS 3.1.1 and there is this thing mentioned about in-place re-factoring. "Introduces functionality for in-editor refactoring."
I'm not sure how to use that. Can someone provide an example?

Daniel Rosenwasser

@DanielRosenwasser

sublimeRefactor.mp4

@batraman ^

Sarthak Batra

@batraman

@DanielRosenwasser thank you! this was really helpful!