I'm getting The project file contains invalid options - Unknown Option: allowSyntheticDefaultImports -- does this option have to be added to Atom TypeScript?

@glen-84 yes. This is because we error on unknown options as a convinience for mis-spellings . I see the issue : TypeStrong/atom-typescript#762 so will continue discussion there :rose:

building the project does (sometimes?)

@kpgarrod are you using external transpiler option?

kpgarrod

@kpgarrod

@basarat I'm not sure I know what that means, but I don't think so :smile:

kpgarrod

@kpgarrod

@basarat: I think I figured it out. I had turned on 'beautify on save' for typescript files in atom-beautify earlier in the day. That seems to have caused this problem. Do you want me to raise an issue in github?

Basarat Ali Syed

@basarat

@kpgarrod atom-beautify and atom-typescript don't play nice together ... can't really ... we work off of tsconfig ... they work off of magic < good for general purpose beautifier but not good for typescript project specific beautifier

llgcode

@llgcode

Hi is someone can tell me about new use-strict statement added automatically by atom-typescript?

@basarat Does atom-typescript interfere with the newline characters used by typescript? I have "newLine": "LF" in my tsconfig file, but it's writing the files with CRLF. It seems to work fine when using tsc directly.

llgcode

@llgcode

@glen-84 thanks. So I've changed the default typescript used (last github version) with the one I have installed with npm to keep compatibility for now waiting the 1.8 to be released

@kataras I've seen the minimal look that way. I uninstalled it for myself :). I haven't seen '/div' artifacts.

Gerasimos (Makis) Maropoulos

@removed~kataras

@basarat it's happening for </span also, If I change the language editor to 'Typescript' ( from Typescript (TSX)) it does disappear but no code hint for html inside render()

I'm using Windows 7, I had the same problem with Windows 10 and Ubuntu 15.10 too

I though it will be fixed but no..

Why I have this problem ?

It's the only reason I had to use sublime but I like Atom most..

Marcus

@mjohnsonengr

Aware of this syntax highlighting issue?

Couldn't find an issue, but I'll be surprised if I'm the first one that's noticed it

@basarat

Roderick Gibson

@kniteli

I use jspm for my run time dependencies, but I'm currently having to npm install angular2 just so atom-typescript can resolve the imports and typings. Does anyone have any thoughts on hooking into the jspm packages instead of having to install the npm versions as well?

Basarat Ali Syed

@basarat

Aware of this syntax highlighting issue?

@mjohnsonengr seems like a specialization of TypeStrong/atom-typescript#645

I use jspm for my run time dependencies, but I'm currently having to npm install angular2 just so atom-typescript can resolve the imports and typings. Does anyone have any thoughts on hooking into the jspm packages instead of having to install the npm versions as well?

@kniteli Nope. TypeScript only resolves on node_modules at the moment and hence that is what we support. As far as I know jspm module resolution is being tracked here : Microsoft/TypeScript#5039 but don't think it covers auto impor. Correct me if I am wrong :rose: