These are chat archives for TypeStrong/atom-typescript

9th
Jul 2015
kpgarrod
@kpgarrod
Jul 09 2015 06:35 UTC
@basarat: great, that works, thanks
Miguel Couto
@Mig1st4ck
Jul 09 2015 10:50 UTC
I am getting an error with "Supplied parameters do not match any signature of call target."
where a method is defined as optional parameters
blob
kpgarrod
@kpgarrod
Jul 09 2015 10:58 UTC
@Mig1st4ck I don't know if it matters, but does getAllRows() return something?
Dan Quirk
@danquirk
Jul 09 2015 22:28 UTC
how come I get the 'some dependencies not found, running apm install for you' notification every time I restart Atom?
it always finds what it needs and gets my TypeScript stuff working but it seems like it shouldn't need to do that every time?
Cu3PO42
@Cu3PO42
Jul 09 2015 22:42 UTC
I… don’t get that. Just checked three installations.
Dan Quirk
@danquirk
Jul 09 2015 22:43 UTC
i figured it wasn't normal :)
Cu3PO42
@Cu3PO42
Jul 09 2015 22:45 UTC
What platform are you running on?
Dan Quirk
@danquirk
Jul 09 2015 22:46 UTC
windows
not sure how to debug what's happening
Cu3PO42
@Cu3PO42
Jul 09 2015 22:47 UTC
I checked two Windows installations :/
Did you check if the dependencies are actually installed even though it is claimed they’re not?
Dan Quirk
@danquirk
Jul 09 2015 22:48 UTC
might be win10 related
i'm not sure what dependencies it's actually installing
clicking the notification bubble didn't give me any more info
Cu3PO42
@Cu3PO42
Jul 09 2015 22:48 UTC
I checked an instance running on Win 10
weird
Dan Quirk
@danquirk
Jul 09 2015 22:49 UTC
it's not really a big deal but figured i'd check if anyone had seen the same behavior
Cu3PO42
@Cu3PO42
Jul 09 2015 22:49 UTC
You could compare the node_modules folder beofre and after an Atom start
to see if it actually did install something
Or if it was just the notification
Dan Quirk
@danquirk
Jul 09 2015 22:51 UTC
as in like the global %user%\AppData\Roaming\npm\node_modules?
oh you mean %user%\AppData\Local\atom\app-1.0.2\resources\app\apm\node_modules
there's an \npm\npm_modules in there too though...
Cu3PO42
@Cu3PO42
Jul 09 2015 22:53 UTC
%user%\.atom\packages\atom-typescript\node_modules
if the location on windows wasn’t changed
Dan Quirk
@danquirk
Jul 09 2015 22:56 UTC
blob
Daniel Melo
@daniel-a-melo
Jul 09 2015 22:59 UTC

Newbie question here:

var aList : number[] = [1,2,3]; aList.push(3);

Gives me "Property 'push' does not exist on type '{}'

I must be missing something obvious :S
Cu3PO42
@Cu3PO42
Jul 09 2015 22:59 UTC
I don’t quite understand. I’ll check in my VM once I got this “Critical error” in the shell infrastructure host fixed again
Daniel Melo
@daniel-a-melo
Jul 09 2015 23:00 UTC
The same applies for any property on any built-in type (string, number)
Cu3PO42
@Cu3PO42
Jul 09 2015 23:01 UTC
@daniel-a-melo that code looks perfectly fine
Daniel Melo
@daniel-a-melo
Jul 09 2015 23:02 UTC
@Cu3PO42 It won't auto complete any property of Array for example... I am not sure it is supposed to... Furthermore it shows me those compilation errors
@Cu3PO42 However it does not complain about property of the classes I define
Dan Quirk
@danquirk
Jul 09 2015 23:03 UTC
sounds like something messed up with lib.d.ts maybe?
it compiles fine from the command line right?
Daniel Melo
@daniel-a-melo
Jul 09 2015 23:05 UTC
@danquirk Good shot. It does compile from command line but it shows me error TS2318: Cannot find global type 'Array' and the same for all other builtin classes
Dan Quirk
@danquirk
Jul 09 2015 23:06 UTC
so that's the error you should get if you run tsc with --nolib
you should have lib.d.ts next to tsc.js
how'd you install typescript?
Daniel Melo
@daniel-a-melo
Jul 09 2015 23:07 UTC
@danquirk npm install -g typescript@beta
Dan Quirk
@danquirk
Jul 09 2015 23:08 UTC
gonna guess the @beta bit is messing it up
Daniel Melo
@daniel-a-melo
Jul 09 2015 23:08 UTC
@danquirk lib.d.ts is right there along with tsc.js
Dan Quirk
@danquirk
Jul 09 2015 23:08 UTC
hm
Daniel Melo
@daniel-a-melo
Jul 09 2015 23:10 UTC
@danquirk got it, my tsconfig had "noLib" : true
Dan Quirk
@danquirk
Jul 09 2015 23:10 UTC
yeah you don't want that :)
Daniel Melo
@daniel-a-melo
Jul 09 2015 23:10 UTC
@danquirk All set now. Thank you very much :)
just out of curiosity, in which situation would noLib be useful?
Cu3PO42
@Cu3PO42
Jul 09 2015 23:13 UTC
@danquirk I just fixed up my VM again and I can say that the package folder should be under %user%\.atom\packages for a fresh install
unless you went out of your way to change it
Dan Quirk
@danquirk
Jul 09 2015 23:15 UTC
haven't messed with anything unless I unwittingly checked some unusual option during Atom's install
Cu3PO42
@Cu3PO42
Jul 09 2015 23:15 UTC
you’d probably have to symlink it over to change it
so, yeah, it should be in that folder
Dan Quirk
@danquirk
Jul 09 2015 23:16 UTC
ah ok sorry, i see now
there're way to many folders with npm and atom stuff in different places, i was looking at the wrong one
Cu3PO42
@Cu3PO42
Jul 09 2015 23:17 UTC
no problem
it’s a bit messed up on windows
it makes more sense on *nix all in all
in my opinion, anyway
Dan Quirk
@danquirk
Jul 09 2015 23:18 UTC
yeah I believe it
my mac usually stays at home
Cu3PO42
@Cu3PO42
Jul 09 2015 23:18 UTC
Probably because some folders follow the Windows structure and other’s just stick to the *nix way of doing things
Dan Quirk
@danquirk
Jul 09 2015 23:19 UTC
i have 17 packages under atom_typescript\node_modules
and i don't notice a change when i close and re-open atom
Cu3PO42
@Cu3PO42
Jul 09 2015 23:20 UTC
17 sounds right
Dan Quirk
@danquirk
Jul 09 2015 23:20 UTC
yeah, based on the speed it goes from 'missing dependencies' to 'all set' it couldn't have run a whole lot
Cu3PO42
@Cu3PO42
Jul 09 2015 23:21 UTC
It probably compares installed versions to what is in package.json, though I don’t see why it would do that in the first place either. Have you tried de- and reinstalling atom-typescript?
… the standard solution for every bug
Dan Quirk
@danquirk
Jul 09 2015 23:28 UTC
haha, worth a try