Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 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
  • Aug 06 21:51
    TheEmrio closed #1506
  • Aug 05 14:22
    TheEmrio opened #1506
  • Jul 15 15:40
    Xapphire13 closed #1496
  • Jul 10 13:23
    akonwi opened #1505
  • Jul 10 04:44
    nelson6e65 edited #1504
  • Jul 10 04:40
    nelson6e65 opened #1504
  • Jul 08 06:40
    sshquack closed #846
  • Jun 17 16:02
    akonwi opened #1503
  • Jun 02 18:18
    tanfonto opened #1502
  • May 28 17:11
    jazzdragon opened #1501
  • Apr 29 01:12
    dyping closed #1500
  • Apr 28 06:56
    dyping edited #1500
  • Apr 28 06:54
    dyping edited #1500
  • Apr 26 11:38
    dyping opened #1500
Basarat Ali Syed
@basarat
@hellboy81 its been requested before : TypeStrong/atom-typescript#315 but not supported yet.
I'm keeping an eye on the TypeScript code to see if it officially becomes any easier : Microsoft/TypeScript#4094 / Microsoft/TypeScript#4789 :rose:
Rob Yoder
@robyoder
Anyone know what's up with the URL definition in lib.d.ts? I'm getting Cannot use 'new' with an expression whose type lacks a call or construct signature. when trying to run new URL('https://example.com') which should be perfectly valid
interface URL {
    createObjectURL(object: any, options?: ObjectURLOptions): string;
    revokeObjectURL(url: string): void;
}
declare var URL: URL;
Not sure why URL is defined this way. Anyone else?
Basarat Ali Syed
@basarat
@robyoder because its not supported in all browsers and very importantly (from ms perspective) IE : https://developer.mozilla.org/en-US/docs/Web/API/URL/URL#Browser_compatibility
Rob Yoder
@robyoder
Sure, but I should be able to check that and use it if it is supported. As it is, I just get an error. I can't redefine it either since it's already been declared. @basarat
Basarat Ali Syed
@basarat
@robyoder you can amend it easily. Just add to the URL interface. See https://basarat.gitbooks.io/typescript/content/docs/types/lib.d.ts.html for examples :rose:
Rob Yoder
@robyoder

Thanks. I've done that before, but I was getting mixed up with it earlier, overcomplicating things and it wasn't seeming to work. Just defining

interface URL {
    new(url: string): any;
}

is a good enough hack for now

kpgarrod
@kpgarrod
I am having an issue since about 6.06 with 'go to declaration'. It takes me to the end of the file where the function is declared, not the declaration of the function itself. Anybody else?
Basarat Ali Syed
@basarat
tested.gif
@kpgarrod ^ works fine here. Would need a repro from you if you are experiencing it still. Might be an edge case bug in TypeScript language service :rose:
Ranjit Jhala
@ranjitjhala
This message was deleted

Hi all, my atom-typescript mysteriously stopped working with this:

In file included from ../fsevents.cc:6:
In file included from ../node_modules/nan/nan.h:74:
In file included from ../node_modules/nan/nan_new.h:181:
../node_modules/nan/nan_implementation_12_inl.h:172:66: error: too many arguments to function call, expected at most 2, have 4
  return v8::Signature::New(v8::Isolate::GetCurrent(), receiver, argc, argv);
         ~~~~~~~~~~~~~~~~~~                                      ^~~~~~~~~~
/Users/rjhala/.atom/.node-gyp/.node-gyp/0.30.6/deps/v8/include/v8.h:4515:3: note: 'New' declared here
  static Local<Signature> New(
  ^
1 error generated.
make: *** [Release/obj.target/fse/fsevents.o] Error 1
gyp ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/Applications/Atom.app/Contents/Resources/app/apm/node_modules/npm/node_modules/node-gyp/lib/build.js:269:23)
gyp ERR! stack     at ChildProcess.emit (events.js:98:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:810:12)
gyp ERR! System Darwin 14.5.0
gyp ERR! command "node" "/Applications/Atom.app/Contents/Resources/app/apm/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Users/rjhala/.atom/packages/atom-typescript/node_modules/grunt-ts/node_modules/chokidar/node_modules/fsevents
gyp ERR! node -v v0.10.30
gyp ERR! node-gyp -v v2.0.2
gyp ERR! not ok 

npm ERR! Darwin 14.5.0
npm ERR! argv "/Applications/Atom.app/Contents/Resources/app/apm/bin/node" "/Applications/Atom.app/Contents/Resources/app/apm/node_modules/npm/bin/npm-cli.js" "--globalconfig" "/Users/rjhala/.atom/.apm/.apmrc" "--userconfig" "/Users/rjhala/.atom/.apmrc" "rebuild" "--target=0.30.6" "--arch=x64"
npm ERR! node v0.10.40
npm ERR! npm  v2.13.3
npm ERR! code ELIFECYCLE
npm ERR! fsevents@0.3.5 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the fsevents@0.3.5 install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the fsevents package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls fsevents
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/rjhala/.atom/packages/atom-typescript/npm-debug.log

Any idea whats going on?

Basarat Ali Syed
@basarat
@ranjitjhala Has to be some library (here : https://github.com/TypeStrong/atom-typescript/blob/master/package.json#L43-L59) that does file watching ... and is using an older version of fsevents that no longer compiles.
@ranjitjhala a longer log + issue report would help :rose:
Ranjit Jhala
@ranjitjhala
@basarat -- thanks, will post issue asap!
Ranjit Jhala
@ranjitjhala
Hi @basarat -- just posted TypeStrong/atom-typescript#583
Basarat Ali Syed
@basarat
@ranjitjhala reply was posted in issue
kpgarrod
@kpgarrod
Help! My atom-typescript is broken. I just updated Atom to 1.0.13 and atom-typescript to 6.0.10 and I get a bug icon in the bottom-right
"Some installed packages could not be loaded because they contain native modules that were compiled for an earlier version of Atom.Rebuild Packages"
I tried rebuilding packages but it didn't work
kpgarrod
@kpgarrod
tried removing and reinstalling the plugin - that didn't work either
Ranjit Jhala
@ranjitjhala
@kpgarrod -- you might be having the same issue as me. (I had similar symptoms, click the "rebuild packages" to see if its this or something else)
Basarat Ali Syed
@basarat
@kpgarrod / @ranjitjhala should be fixed with 6.0.12 :rose:
Just more info : Got lucky this time as it wasn't a core dependency and just devDependencies (we did have dependency on chokidar at some point but decided to just use fs and only watch tsconfig.json)
kpgarrod
@kpgarrod
@basarat: Thanks. It is fixed for me in 6.0.11 :)
Robert Knight
@robertknight
I've got a problem with project rebuilds (TypeScript -> Build) taking an exceedingly long time (or perhaps timing out eventually, it isn't clear). What is available in the way of debugging tools?
No errors visible in the Atom dev tools
Yousef Shanawany
@AskYous
Does typescript allow for imports from other .ts files?
Ranjit Jhala
@ranjitjhala
That was super fast, thanks a bunch @basarat !!!
Johan Alkstål
@johanalkstal

Hi! Just getting started with TS and atom-typescript.
For some reason changes to my .ts files have stopped getting added to the compiled .js file. The .js files are not getting updated and my latest .ts file just compiles to an empty .js file.

I'm sure I've configured it wrong or something. :) But does anyone have a clue?

Johan Alkstål
@johanalkstal
OK, seems like tsconfig.json didn't like the outFile option. Changed it to outDir and now it works.
But "outFile" should work though?
saviilsy
@saviilsy
Hi! Just installed atom-typescript however it complains about "Cannot find module "ntypescript""
Basarat Ali Syed
@basarat

Does typescript allow for imports from other .ts files?

@AskYous yes. Use external modules e.g. --module commonjs. More : https://basarat.gitbooks.io/typescript/content/docs/project/modules.html

But "outFile" should work though?

@johanalkstal outFile is not a valid compiler option. Perhaps you meant out. But we don't recommend it https://github.com/TypeStrong/atom-typescript/blob/master/docs/out.md

Hi! Just installed atom-typescript however it complains about "Cannot find module "ntypescript""

@saviilsy more info please :rose: . Perhaps create an issue

Rob Yoder
@robyoder
three.png
Today, out of the blue, my TS syntax highlighting broke. I reverted to an older version of atom-typescript, but that didn't change anything. But I don't understand what else could be to blame for TS syntax highlighting issues. Basically it doesn't like the second and third parameters there
one.png
Reducing it to one fixes the syntax highlighting but is incorrect and appropriately gives an error
Any ideas?
There is no newline between the first and second type arguments there and even when the three type arguments are short enough to fit on one line it doesn't work
David Driscoll
@david-driscoll
Some have reported reverting atom versions have fixed the issue
Cu3PO42
@Cu3PO42
I just saw the SOS mention. Something must be terribly broken.
This is so. Weird.
Rob Yoder
@robyoder
@david-driscoll thanks, that worked for me. One of my colleagues was using 1.0.15 successfully, so I switched to that one and it works fine. I was on 1.0.18, haven't tested 1.0.19 yet.
Marco Visintin
@m3kka
hello there - is there a changelog for this package somewhere?
Basarat Ali Syed
@basarat