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
Matt Traynham
@mtraynham
Off master yes
Ronn
@ronnross
awesome thanks @mtraynham
Mike Graham
@cmichaelgraham
they are in 1.5, but work great in Atom-TypeScript - here's a sample repo - look in here - in this file
Ronn
@ronnross
thanks @cmichaelgraham !!
Mike Graham
@cmichaelgraham
you bet :)
Ronn
@ronnross
I believe atom-typescript is generating both a *.js and tsconfig.json file for all files I edit with a .ts extension.
is there any way to suppress those files from being generated? I just want webpack to worry about transpiling the ts files
Mike Graham
@cmichaelgraham
i'm not getting a tsconfig.json for each .ts. do you have a tsconfig.json somewhere up the folder hierarchy?
Ronn
@ronnross
I'm sorry I was mistaken it is only generating one. So that is not an issue.
Mike Graham
@cmichaelgraham
ah - cool :)
Steve Ognibene
@nycdotnet
Bas - is your talk tomorrow going to be recorded?
Basarat Ali Syed
@basarat
@nycdotnet nope. But I'll try and create a youtube video once I have more of the stuff done. Although I am quite happy with the amount of stuff we have : https://github.com/TypeStrong/atom-typescript/#features but there is a lot more to be done :heart:
Steve Ognibene
@nycdotnet
I'm certainly impressed. Hey - I should drop the next grunt-ts with Visual Studio project file support shortly.
Basarat Ali Syed
@basarat
sweet :candy:
Steve Ognibene
@nycdotnet
NPM says the next release will be number 100
Basarat Ali Syed
@basarat
:confetti_ball:
Patrick Toy
@patrickjtoy
Hey all, having some difficulty getting my project to compile via atom-typescript. It hangs in the same place consistently, w/o throwing an error. I've verified that the project does compile with tsc from the command line. Has anyone else seen the same issue?
Basarat Ali Syed
@basarat
@patrickjtoy no. Can I have a look at the source?
Patrick Toy
@patrickjtoy
@basarat sure, here's the source file that I was referencing where the atom-typescript compiler stalls: http://pastebin.com/mSf8aTsL
Patrick Toy
@patrickjtoy
@basarat just got an update to atom-typescript 2.6.1, the compiler is no longer stalling at the above-referenced script. Still having issues completing the build, but I'll need to research where it's getting stuck now.
Basarat Ali Syed
@basarat
compileonsave.gif
@patrickjtoy Seems to compile / build fine. I'd be happy to look at an example if you still have issues.
Mike Graham
@cmichaelgraham
can you point me at some guidance to set up karma to build and watch typescript source files, build them, and run associated jasmine tests? i want this to be running while i edit in atom-typescript
i would like to use the same typescript compiler atom-typescript is using
Basarat Ali Syed
@basarat
@cmichaelgraham not a good story at the moment. One would need to write something like : https://github.com/karma-runner/karma-coffee-preprocessor using https://github.com/teppeis/typescript-simple#source-map but TSS needs to be upgraded to use the atom-typescript version of TS
Matt Traynham
@mtraynham
@basarat Looking for someone fluent in TypeScript. Is export import still allowed when using ES6 import syntax?
export import Foo from './Foo';
class Foo {
 ....
}
export default Foo;
Basarat Ali Syed
@basarat
blob
@mtraynham guess not
Basarat Ali Syed
@basarat
blob
but you don't need to come up with new names like we needed before ^
There might be a simpler syntax out there that still makes ts happy :smiley:
Michael
@michaelsg
export Foo from './Foo'
Basarat Ali Syed
@basarat
blob
@michaelsg TS is a bit fidgetty with it at the moment
Michael
@michaelsg
yeah, I know.
Bruce Mitchener
@waywardmonkeys
I think I'm using export import ... in a project using 1.5.0-alpha
I forgot to sleep last night though, so I'll double check.

index.js:

export import CFG = require('./cfg');
export import HavlakLoopFinder = require('./havlak');

elsewhere:

import {CFG} from './node_modules/code-analysis/lib/index';

var bb = new CFG.BasicBlock(1);
I'm inordinately proud of having gotten that working. :worried:
Basarat Ali Syed
@basarat
@waywardmonkeys cool first one is commonjs module syntax @mtraynham wants an export import for ES6 import / from syntax
Matt Traynham
@mtraynham
right, I have the commonjs syntax working
Bruce Mitchener
@waywardmonkeys
ohhhh.
Matt Traynham
@mtraynham
I imagine the need to support bundled modules is becoming less & less with ES6
so I don't know if anyone has needed this case yet...
Bruce Mitchener
@waywardmonkeys
what are bundled modules ? When you use dts-bundler or dts-generator?
Matt Traynham
@mtraynham
bundled as in Webpack or Browserify
Bruce Mitchener
@waywardmonkeys
oh, I don't do that sort of thing.