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
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
@greatelv would like to add ... definitely consider using commonjs and not having multiple tsconfig.json files
@greatelv with webpack
:rose:
Jeon, TaeKyung
@greatelv
Thanks your answer!
Eric Credeur
@proff321
Hello everyone! I've been fighting with an error that claims that a file "is not included in the TypeScript compilation context." I looked over the documentation and discovered that you have to add the "files":{} property to the tsconfig.json file. I've done so via the "filesGlob":[] property and the auto-generated file list includes the file in question. I've even gone as far as to relocated the project to a path with no spaces wondering if that is the source of the issue. At this point, I've run out of options and welcome any suggestions.
Roni Frantchi
@roni-frantchi

hi all!. quick question..
it seems like node_modules content gets compiled and spits out tons of errors when run build (F6),
that's in spite of my jsconfig.json having
"exclude": [ "node_modules/*", "examples/*" ]
have also tried "files": [ "src/app/app.ts", }
nothing sticks. still lots of:

ideas?..

Eric Credeur
@proff321
Hello @roni-frantchi, I've been fighting with tsconfig.json issues this morning as well.
Have you tried adding !node_modules/** to the "filesGlob":[] property and then have it rebuild the file list?
Roni Frantchi
@roni-frantchi
hi @proff321 have just seen your post. seems like you're on the other end of the spectrum - and it won't include any file for you ..?
Eric Credeur
@proff321
Well, I tried not including any files at all and I still get the error in my case. No matter what I do, atom continues to tell me that the file in not in the compiler's context.
Roni Frantchi
@roni-frantchi
@proff321 have you tried not specifying the files property at all? supposedly this will force it to include any and all files
Eric Credeur
@proff321
Yep. And I just tried it again to make sure that it was something I tested.