Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 15:49
    kulikalov opened #1540
  • 00:04
    lierdakil closed #1535
  • 00:01
    github-actions[bot] closed #231
  • 00:01
    github-actions[bot] closed #316
  • 00:01
    github-actions[bot] closed #398
  • 00:01
    github-actions[bot] closed #780
  • 00:01
    github-actions[bot] closed #800
  • 00:01
    github-actions[bot] closed #801
  • Jan 19 00:01
    github-actions[bot] closed #803
  • Jan 19 00:01
    github-actions[bot] closed #807
  • Jan 19 00:01
    github-actions[bot] closed #808
  • Jan 19 00:01
    github-actions[bot] closed #811
  • Jan 19 00:01
    github-actions[bot] closed #822
  • Jan 19 00:01
    github-actions[bot] closed #825
  • Jan 17 23:32
    reduxdj edited #1539
  • Jan 17 23:32
    reduxdj opened #1539
  • Jan 17 14:52
    lierdakil labeled #1483
  • Jan 17 14:51
    lierdakil closed #1508
  • Jan 17 14:51
    lierdakil labeled #1508
  • Jan 17 14:50
    lierdakil labeled #1511
Blake Embrey
@blakeembrey
if they were from typing install d3, they are external modules
not global
so the name d3 will not exist in scope
you should probably be getting d3 by doing import * as d3 from 'd3'
Ben
@eenblam
Okay, so I should probably give context. I just started with TypeScript today. I went through most of the Handbook, and then I tried opening up a simple d3 app I'd written to figure out how to annotate it properly.
Okay, cool.
Gustav Bylund
@Maistho
There's probably global typings for d3 as well
Ben
@eenblam
That fixed d3, but RXJS (typings install rx) did install into globals yet isn't being found.
(even if I try importing)
Gustav Bylund
@Maistho
rx probably needs to be included as well. I recall adding import 'rxjs/Rxjs' somewhere
Ben
@eenblam
Tried import * as Rx from 'rx' and import 'rxjs/Rxjs'. Still can't find Rx.
Blake Embrey
@blakeembrey
how did you install them from global? i'm going to assume it's this: https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/rx/rx.d.ts
the correct way to import would be import rx = require('rx') (but import * as rx from 'rx' should also work)
make sure it's also installed
Ben
@eenblam

I got this:

$ typings install dt~rx
typings ERR! message Attempted to compile "rx" as an external module, but it looks like a global module. You'll need to enable the global option to continue.

so I did this:

$ typings install dt~rx --global
typings INFO reference Stripped reference "https://raw.githubusercontent.com/DefinitelyTyped/DefinitelyTyped/7de6c3dd94feaeb21f20054b9f30d5dabc5efabd/rx/rx-lite.d.ts" during installation from "rx" (main)
rx
└── (No dependencies)
Blake Embrey
@blakeembrey
yes, and there's a reference stripped during installation
so you can do typings install dt~rx-lite --global to correct that
it's an unfortunate problem with dependency management in the definitelytyped source
Ben
@eenblam
Did so, still can't find 'Rx'
Blake Embrey
@blakeembrey
rx lowercase
aside from that, it seems correct to me
can you make sure it's not just a restart of atom or something else required
try compiling with tsc?
Ben
@eenblam
Restarted atom
Lowercase rx? I can't just import Rx = require('rx');?
Apparently not. This fixed it.
import rx = require('rx');
let Rx = rx;
(I had Rx.Observable.etc() in the original .js file.)
@blakeembrey Thanks for the help!
Blake Embrey
@blakeembrey
that's really odd, the variable name causing shouldn't have mattered
glad you've got it working now :)
Ben
@eenblam
Yeah, I'm super confused still, but I guess it's working.
The JS ecosystem as a whole is pretty new to me. I should probably read up CommonJS and on TypeScript's namespacing to get a better handle on what's going on here.
Ben
@eenblam
@blakeembrey I didn't observe the same behavior with casing when I booted up my computer this morning.
There were other errors popping up for another module that doesn't have a declaration file yet along with some errors regarding the number of arguments d3 expects in its callbacks. I must have just misread something.
Valentin Robert
@Ptival
so it atom-typescript shipping TypeScript 2.0 now? I can use strictNullChecks, nice! :)
Žygimantas
@benetis

Hey,
atom-typescript shows error on angular2 components near:

    moduleId: module.id,     <Cannot find name 'module'>

Any ideas what could I do to make this disappear? Angular build and there are not problems. Thanks in advance!

Žygimantas
@benetis
@benetis Answer > You need explicitly import typings for this to work.
Tucker Lein
@tlein
hello, anyone experiencing atom-typescript 8.11.0 freezing atom 1.8.0 when atom starts up on windows?
when I remove the plugin from my .atom directory it works, definitely seems to be atom-typescript. Also I was using it earlier today, I believe it was still version 8.11.0, but suddenly it just started freezing atom, not aware of anything that changed
Tucker Lein
@tlein
nevermind, opening a blank atom without the project directory and re-adding it seems to have fixed the issue
jtuu
@jtuu
hi, i updated to atom-typescript 9.0.0 today and now it's saying it can't find tsconfig.json. did something change with that?
Dmitry Petrov
@satanworker
Hi, guys, is really loved atom, and want to switch from Webstorm for some cases, but is there are any way to configure auto import of classes like in jetbrains?
For me it's killer feature, and really don't get why it's implemented only in WebStorm
atsu85
@atsu85
I'm also missing it A LOT - every time i have to manually import smth, I'm regretting I'm not using WebStorm ;)
otherwise Atom is great, keep up the good work!
David Sancho
@davesnx
Hey guys, I search on the issues and I coudn't find it. There's a reason why u are using react@0.13 and not 15.0? and also, there's a reason why u are not using react-for-atom?
I would try to upgrade the version on the package and try it if it works, and open a PR?
That sounds correct to everybody? ^^
Basarat Ali Syed
@basarat
I added react a while back just to experiment with it. The only thing that uses it is the semantic view. That view is starting to show its age. I had to rewrite the backend for that when I migrated it to alm.tools : https://github.com/alm-tools/alm/blob/master/docs/features/semantic-view.md so at this point its one of those features in atom-typescript that require continuous love and better removed to make maintainance easier :rose: