Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 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
  • 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
Basarat Ali Syed
@basarat
@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.
Roni Frantchi
@roni-frantchi
@proff321 at the risk of sounding like your system admin.. did you try to close and reopen atom? i think i read somewhere that you should or it won't detect this sort of changes.. anyway it did not help for me but maybe you're in luck
@proff321 !node_modules/** didn't help either btw
@proff321 it actually generated the files to include all that's under node_modules/** funny the ! didn't catch on
Eric Credeur
@proff321
LOL, well at least my filesGlob:[] is following the ignores.
Hmmm, do you have your base code folder placed in a DropBox (or something similar) directory?
Eric Credeur
@proff321
Well, it looks like my issue could be related to some type of bug.
Roni Frantchi
@roni-frantchi
@proff321 nope. no spaces orr odd characters either.
Eric Credeur
@proff321
I just figured out that if you click on the error it will open a ton of tabs that all link to the same file.
Roni Frantchi
@roni-frantchi
@proff321 how so? what'd you find?
Eric Credeur
@proff321
If you click on the file in one of the tabs that just opened, the error goes away.
Roni Frantchi
@roni-frantchi
@proff321 ouch.
Eric Credeur
@proff321
Well, it looks like I'm filing a bug.
One more thought for you @roni-frantchi have you tried removing all of the files:{} and excludes:{} and re-generating them from the filesGlob:[] property?
If you try this, make sure that you do no leave a trailing comma after the "fileGlobs":[] property, otherwise it will not generate the "files":{} property.
Roni Frantchi
@roni-frantchi
@proff321 thanks. still no luck. i also tried "filesGlob": [ "src/**" ] but it just seem to cause the build progress to start and just hang in there.. so weird
Basarat Ali Syed
@basarat

@proff321

Tips : files and exclude (note not excludes ... and I did argue for it ... https://github.com/Microsoft/TypeScript/pull/3188#issuecomment-102720217 but they went with exclude ¯\_(ツ)_/¯) are both arrays ... so files:{} is bad files:[] is good (same for exclude). Also `exclude should just be directory name (
"exclude": [ "node_modules", "examples" ])

PS: feel free to file a :bug: :rose:
Rob Yoder
@robyoder

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:

Awesome! :heart:

I need to check back here more often :)
Basarat Ali Syed
@basarat
You can click watch on an issue on github to get notified when that issue is resolved/closed ;)
Valentin Robert
@Ptival
@basarat thanks for the merge! as part of building on my system, I had an error in tsconfig.d.ts about not finding the module 'pinkie-promise', any pointer on that?
Basarat Ali Syed
@basarat
@Ptival That is a bug (a bit harmless though) in the tsconfig.d.ts file and an issue needs to be reported /cc @blakeembrey
I had the same error when building locally (which I just ignored) before pushing ;)
Blake Embrey
@blakeembrey
yeah, i have the same issue but there's no proper fix for the bug in tsconfig until i've finished with tsd :( if i define pinkie-promise, it might conflict with a different definition - the simplest fix is to copy it locally to your own project (which i did with ts-node)
Rob Yoder
@robyoder
ts-grammar.png
@basarat new grammar problem, known issue?
using parentheses seems to be the issue
Blake Embrey
@blakeembrey
TypeStrong/atom-typescript#670
recently logged the same issue
Rob Yoder
@robyoder
gracias!
matthew harwood
@matthewharwood
anyone know within a tsconfig.json the purposes of these flags
        "declaration": false,
        "noImplicitAny": false,
        "noLib": false,
matthew harwood
@matthewharwood
mmm Tyty
James Brantly
@jbrantly
if you have specific questions after reading that feel free to ask :D