Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Dec 05 17:51
    lierdakil synchronize #1527
  • Dec 05 16:20
    lierdakil edited #1527
  • Dec 05 16:15
    lierdakil opened #1527
  • Dec 05 06:59
    lierdakil closed #1503
  • Dec 05 06:59
    lierdakil closed #1509
  • Dec 05 05:43
    lierdakil labeled #1502
  • Dec 05 05:43
    lierdakil closed #1502
  • Dec 05 05:24
    lierdakil labeled #1513
  • Dec 05 05:24
    lierdakil labeled #1513
  • Dec 05 05:24
    lierdakil labeled #1510
  • Dec 05 01:28
    lierdakil closed #1523
  • Dec 02 10:12
    jeremy-flusin synchronize #1523
  • Nov 27 12:59
    jeremy-flusin synchronize #1523
  • Nov 27 09:57
    jeremy-flusin synchronize #1523
  • Nov 27 09:51
    jeremy-flusin synchronize #1523
  • Nov 26 20:46
    jeremy-flusin synchronize #1523
  • Nov 26 20:41
    jeremy-flusin synchronize #1523
  • Nov 25 20:43
    jeremy-flusin edited #1523
  • Nov 25 20:41
    jeremy-flusin synchronize #1523
  • Nov 25 18:58
    lierdakil synchronize #1523
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"

Valentin Robert
@Ptival
@basarat is child_process part of your codebase or something from a library?
oh seems like it's a node thing
Basarat Ali Syed
@basarat
TIP my workflow: if a require name is not relative -> check package.json if not there ... probably a node thing, otherwise lookup on npmjs.com
also the node built-ins are in js as well in the lib folder : https://github.com/nodejs/node/tree/master/lib (they interact with the C code base using process.binding)
Basarat Ali Syed
@basarat
^ just thought I'd share the knowledge (that was hard for me to come by) :rose:
Valentin Robert
@Ptival
thanks, that's useful
Matteo Gabriele
@MatteoGabriele
please somebody helps me! :D
Basarat Ali Syed
@basarat
@MatteoGabriele Whatcha need help with?
Filipe Silva
@filipesilva
heya, just a quick question
is there a way to only load atom-typescript when a tsconfig.json is present?
(I ask because it's timecop shows it as the package with bigger load time, and I'd like to avoid that on projects that aren't typescript based)
Matteo Gabriele
@MatteoGabriele
I'm trying to add a typescript project that hasn't a tsconfig.json file in it, if I try to add it in atom works, it hands all the libraries but then everything seems broken. I colleague has the same env but for him is working, even if he passed me a pre-made tsconfig file. for me doesn't make any sense.
Matteo Gabriele
@MatteoGabriele
sorry there are a lot of type errors ahahahha don't know why :D
but the problems should be clear....I hope so
Basarat Ali Syed
@basarat

I'm trying to add a typescript project that hasn't a tsconfig.json file in it, if I try to add it in atom works, it hands all the libraries but then everything seems broken. I colleague has the same env but for him is working, even if he passed me a pre-made tsconfig file. for me doesn't make any sense.

@MatteoGabriele I am confused by the query. Sorry can you rephrase :rose:

heya, just a quick question

We try to delay as much as possible till a .ts file is opened in atom. But there are other performance things that still need to be done

Filipe Silva
@filipesilva
@basarat thanks for clarification!
ComFreek
@ComFreek
Where can I find the "Create tsconfig.json project file" command?
I cannot find it in the Packages menu.