Thanks for the help :)
Btw, I greatly appreciate all of the software you've contributed for Typescript, as a frequent typescript dev it's aided me a lot over the past year. At this point seeing your name on a project gives me more confidence that I can depend on it, atom-typescript was a factor in my switching from sublime to atom
@wjswjs2
apm uninstall atom-typescript / apm install atom-typescript
however you probably want the latest grammar work that @Cu3PO42 's been doing, ... so fork? Or PR / Issue ... guess there is a user demand for it ... so would be okay with maintaining it
look at
atomConfig.ts in the repo ... if you create an issue I'll mark it up for grabs :rose:
@tcarlsen are you going to create that issue? Should I?
maybe splitting up atom-typescript into services (like autocomplete+ did) would be the best way?
but to answer your question,… You go ahead and create the issue :smile:
released
Hi folks, got a little question. I've lowercased the filename of one of my source files, now atom complains that this file is not listed in tsconfig.json but on save it compiles the file with old camel cased name to the output directory. Syncing files does not help, so is there a something like a cache I can additionally clear?
That seems not very robust...?
I'd like to use import from, but it seems like that's not compatible with the dts files produced by the typescript compiler
I'd have to manually edit those dts files I guess?
Hi, what are the best practices for writing a library in typescript that is then consumed by another typescript library? Is it really to manually ///<reference> the output file?
@CannibalVox No just use commonjs with declaration true. A quickstart : http://basarat.gitbooks.io/typescript/content/docs/node/nodejs.html
Also is there any way to not compile to a single file but have the compiled output not be mixed in with the source?
Also is there any way to not compile to a single file but have the compiled output not be mixed in with the source?
You can use outDir. But I recommend against that as it becomes fairly weird ... fairly quickly
because the root of my source files looks like this:
namespace TechnicCommon {
export class VersionedResource extends WebResource {
export class VersionedResource extends WebResource {
is that not correct?
But http://basarat.gitbooks.io/typescript/content/docs/project/namespaces.html shows quite the opposite
Okay, I have two classes that are in the same exported module, one inherits from the other and both need to be available to consumers. I've tried marking just the module for export, but in that case the class doesn't appear in the DTS file. If I mark the class for export, though, it's not marked as export in the DTS file. This seems like it's probably fine, but when compiling the child class it gives me an "all export or all local" error. This happens even when I'm importing directly from the TS file, though.