Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Nov 01 19:20
    dependabot[bot] labeled #1521
  • Nov 01 19:20
    dependabot[bot] opened #1521
  • Oct 26 23:07
    lierdakil closed #1512
  • Oct 26 23:07
    lierdakil labeled #1512
  • Oct 26 23:07
    lierdakil labeled #1512
  • Oct 24 22:12
    micazoyolli opened #1520
  • Oct 23 23:07
    lierdakil closed #1514
  • Oct 23 23:06
    lierdakil labeled #1514
  • Oct 23 22:53
    lierdakil closed #1518
  • Oct 23 22:53
    lierdakil closed #1517
  • Oct 23 22:52
    lierdakil closed #1516
  • Oct 23 22:51
    lierdakil opened #1519
  • 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
phil
@uniphil
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.
Philipp Knecht
@fopsdev
@ComFreek Ctrl-Shift-P should open the command menu
Jeon, TaeKyung
@greatelv
master @basarat. i have a question
the problem is multiple tsconfig files in project.
Error message is "a.ts is not included in the Typescript compilation context. If this is not intended, please check the 'Files', 'filesClob' section of your tsconfig.json file.
Jeon, TaeKyung
@greatelv
I hope to set a specific tsconfig in project
one thing out of multiple tsconfig..
is possible ?
Basarat Ali Syed
@basarat

@greatelv say you have :

root
| > tsconfig.json
|> a.ts
|> somedir
           |>  tsconfig.json
           |>  b.ts

then if you open a.ts the root tsconfig.json is activated ... and used ... even for b.ts

does that answer your question?
Jeon, TaeKyung
@greatelv
um... in my case, the sub tsconfig in somedir is activated for b.ts
if i remove tsconfig in somdir, then root tsconfig activated
Basarat Ali Syed
@basarat
@greatelv even after you open a.ts?
Jeon, TaeKyung
@greatelv
!?
if i first access the b.ts, not working.
but first a.ts, next accessing b.ts is working
Basarat Ali Syed
@basarat
@greatelv yup. That is by design. We cache the tsconfig.json against each file. So if root tsconfig is parsed ... it is marked for b.ts as well and then used for b.ts as well and no lookup is performed in somedir
So if working on b.ts project ... only have b.ts file open
if working on a.ts project ... have a.ts opened at least once
@greatelv at any point you can refresh the cache by closing all files of the non desired project and run sync command
Jeon, TaeKyung
@greatelv
oh, i didn't know that
Basarat Ali Syed
@basarat
A better UX would a project selector that shows the tsconfig.json files available in current working dir