Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Oct 19 14:49
    betheymc opened #1518
  • Oct 19 14:43
    betheymc opened #1517
  • Oct 19 14:36
    betheymc opened #1516
  • Oct 19 14:30
    betheymc opened #1515
  • Oct 15 09:28
    pasinduperera synchronize #1514
  • Oct 15 09:20
    pasinduperera synchronize #1514
  • Oct 15 09:11
    pasinduperera opened #1514
  • Oct 02 22:01
    kaiyoma opened #1513
  • Sep 30 20:20
    jfellus edited #1512
  • Sep 30 20:20
    jfellus edited #1512
  • Sep 30 20:19
    jfellus edited #1512
  • Sep 30 20:18
    jfellus edited #1512
  • Sep 30 20:18
    jfellus edited #1512
  • Sep 30 20:17
    jfellus opened #1512
  • Sep 21 09:57
    arcanis opened #1511
  • Sep 20 16:18
    reduxdj edited #1510
  • Sep 20 16:18
    reduxdj opened #1510
  • Sep 20 08:28
    mininek opened #1509
  • Aug 15 17:06
    chaffeqa opened #1508
  • Aug 08 16:07
    lierdakil closed #1507
Johan Alkstål
@johanalkstal

Hi! Just getting started with TS and atom-typescript.
For some reason changes to my .ts files have stopped getting added to the compiled .js file. The .js files are not getting updated and my latest .ts file just compiles to an empty .js file.

I'm sure I've configured it wrong or something. :) But does anyone have a clue?

Johan Alkstål
@johanalkstal
OK, seems like tsconfig.json didn't like the outFile option. Changed it to outDir and now it works.
But "outFile" should work though?
saviilsy
@saviilsy
Hi! Just installed atom-typescript however it complains about "Cannot find module "ntypescript""
Basarat Ali Syed
@basarat

Does typescript allow for imports from other .ts files?

@AskYous yes. Use external modules e.g. --module commonjs. More : https://basarat.gitbooks.io/typescript/content/docs/project/modules.html

But "outFile" should work though?

@johanalkstal outFile is not a valid compiler option. Perhaps you meant out. But we don't recommend it https://github.com/TypeStrong/atom-typescript/blob/master/docs/out.md

Hi! Just installed atom-typescript however it complains about "Cannot find module "ntypescript""

@saviilsy more info please :rose: . Perhaps create an issue

Rob Yoder
@robyoder
three.png
Today, out of the blue, my TS syntax highlighting broke. I reverted to an older version of atom-typescript, but that didn't change anything. But I don't understand what else could be to blame for TS syntax highlighting issues. Basically it doesn't like the second and third parameters there
one.png
Reducing it to one fixes the syntax highlighting but is incorrect and appropriately gives an error
Any ideas?
There is no newline between the first and second type arguments there and even when the three type arguments are short enough to fit on one line it doesn't work
David Driscoll
@david-driscoll
Some have reported reverting atom versions have fixed the issue
Cu3PO42
@Cu3PO42
I just saw the SOS mention. Something must be terribly broken.
This is so. Weird.
Rob Yoder
@robyoder
@david-driscoll thanks, that worked for me. One of my colleagues was using 1.0.15 successfully, so I switched to that one and it works fine. I was on 1.0.18, haven't tested 1.0.19 yet.
Marco Visintin
@m3kka
hello there - is there a changelog for this package somewhere?
Basarat Ali Syed
@basarat
Kitson Kelly
@kitsonk
#630 is doing my head in. Going to try to downgrade to atom 1.0.15.
Kitson Kelly
@kitsonk
Downgrading does work, but of course, the auto-update feature keeps trying to get me to move back to a broken version.
Valentin Robert
@Ptival
has anyone tried using atom-typescript under NixOS? It seems it tries to access libgtk-x11-2.0.so which crashes the ts worker
Basarat Ali Syed
@basarat
@Ptival I haven't
NOTE ALL (I don't like all mention so not using it) the grammar breaking in 1.0.15 was fixed with version 7.1 of this package :rose:
Valentin Robert
@Ptival
@basarat would you happen to know which part of the atom-typescript code would require that shared library?
Basarat Ali Syed
@basarat
@robyoder / @kitsonk ^
@Ptival you can open up debug.tsand edit it to make it run synchronously ... that might give you more help
Valentin Robert
@Ptival
ah, thanks, I'll give this a try
phil
@uniphil
@Ptival I've been having the same issue -- I thought it was because nix's Atom package was back at 1.0.4, but upgrading it to 1.0.19 has not helped
Valentin Robert
@Ptival
@uniphil so did you just give up on it?
phil
@uniphil
finding your nixos github issue and this chat has given me optimism :)
I actually just figured out how to override the atom package earlier this evening
phil
@uniphil
When I open any typescript file, this is what happens in the console: https://i.imgur.com/xVBy9Jy.png
many times per second
and my fan spins up and my laptop gets hot :)
Valentin Robert
@Ptival
@uniphil yes, same here
phil
@uniphil
I'm not having much luck debugging so far. Setting everything in debug to true does not stop the worker from dying/restarting constantly nor change the message.
in workerLib I can stop the worker from restarting if the code is 127, but then I can't open typescript files
Basarat Ali Syed
@basarat
@uniphil @Ptival Ive created this issue TypeStrong/atom-typescript#642
phil
@uniphil
cool
Basarat Ali Syed
@basarat
@uniphil @Ptival issue closed. Try now :rose:
Kitson Kelly
@kitsonk
@basarat thank you much! It is working for me.
Valentin Robert
@Ptival
@basarat neither apm install nor npm install seem to refresh the .js files in my dist/ directory, am I missing something?
Basarat Ali Syed
@basarat

neither apm install nor npm install seem to refresh the .js files in my dist/ directory, am I missing something?

@Ptival atom-typescript is built with atom-typescript .... I can see why this can be a pain if you don't have a working atom-typescript in the first place. There is grunt there in the repo ... but it hasn't been maintained for quite a while so YMMV. If it doesn't work let me know and I'll try to fix it :rose:

npm install grunt grunt-ts and then grunt
@Ptival we had to remove it because atom wasn't liking it TypeStrong/atom-typescript#600
Valentin Robert
@Ptival
@basarat I guess it's fine, good news is setting debug to true fixes the NixOS issue, so my guess is startWorker passes an environment to the spawned process that does not work well with NixOS
phil
@uniphil
with debug true atom-typescript is finally working for me too!
Basarat Ali Syed
@basarat

so my guess is startWorker passes an environment to the spawned process that does not work well with NixOS

Guess so :worried: BufferedProcess was a pain to get working on windows as well, but we managed to do that atom/atom#2887 Its because of us using atom as node (and not taking an unneeded dependency). Perhaps we can add an option "use node as node"