Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Aug 15 17:06
    chaffeqa opened #1508
  • Aug 08 16:07
    lierdakil closed #1507
  • Aug 08 16:07
    lierdakil labeled #1507
  • Aug 08 11:43
    rahamin1 opened #1507
  • Aug 07 12:07
    lierdakil labeled #1505
  • Aug 07 12:07
    lierdakil closed #1505
  • Aug 06 21:51
    TheEmrio closed #1506
  • Aug 05 14:22
    TheEmrio opened #1506
  • Jul 15 15:40
    Xapphire13 closed #1496
  • Jul 10 13:23
    akonwi opened #1505
  • Jul 10 04:44
    nelson6e65 edited #1504
  • Jul 10 04:40
    nelson6e65 opened #1504
  • Jul 08 06:40
    sshquack closed #846
  • Jun 17 16:02
    akonwi opened #1503
  • Jun 02 18:18
    tanfonto opened #1502
  • May 28 17:11
    jazzdragon opened #1501
  • Apr 29 01:12
    dyping closed #1500
  • Apr 28 06:56
    dyping edited #1500
  • Apr 28 06:54
    dyping edited #1500
  • Apr 26 11:38
    dyping opened #1500
kpgarrod
@kpgarrod
"Some installed packages could not be loaded because they contain native modules that were compiled for an earlier version of Atom.Rebuild Packages"
I tried rebuilding packages but it didn't work
kpgarrod
@kpgarrod
tried removing and reinstalling the plugin - that didn't work either
Ranjit Jhala
@ranjitjhala
@kpgarrod -- you might be having the same issue as me. (I had similar symptoms, click the "rebuild packages" to see if its this or something else)
Basarat Ali Syed
@basarat
@kpgarrod / @ranjitjhala should be fixed with 6.0.12 :rose:
Just more info : Got lucky this time as it wasn't a core dependency and just devDependencies (we did have dependency on chokidar at some point but decided to just use fs and only watch tsconfig.json)
kpgarrod
@kpgarrod
@basarat: Thanks. It is fixed for me in 6.0.11 :)
Robert Knight
@robertknight
I've got a problem with project rebuilds (TypeScript -> Build) taking an exceedingly long time (or perhaps timing out eventually, it isn't clear). What is available in the way of debugging tools?
No errors visible in the Atom dev tools
Yousef Shanawany
@AskYous
Does typescript allow for imports from other .ts files?
Ranjit Jhala
@ranjitjhala
That was super fast, thanks a bunch @basarat !!!
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