Robbie Speed

Can be handled fairly easily to allow for expansion of the api with a oddly defined `.gitignore`: ``` * !.gitignore !pakage.json !module.js !lib/* ``` This would allow to add whatever...

@gaetanmaisse using typescript project references would be another option, node types are pulled in now because they are part of the same project as the server which does use the...

Just encountered a use case for this today when writing out a value ref class. ```ts class Ref { readonly value: T; constructor (value: T) { this.value = value; }...

> cases 4 and 5 I think are rare so it is fine for them to require more noisy syntax @mixtur case 4 is what inspired this proposal, so I...

Is the reason for async mainly so that state changes get queued? I agree with @Havunen it would be nice if it was just simplified so `setState` was either always...

I understand, it seems like a very bad design if you can't be sure whether it's going to be async or sync. That should be chosen within the method, not...

@Havunen I could take a look at fixing this, I'm going to be writing inferno integration for my own state management library which functions using a similar observer pattern to...

I would happily switch to deno-lint if it supported a plugin system, preferably one that maintains the most performance while making plugins writable in TS/JS. Eslint plugin compatibility isn't a...

@traceypooh this seems unrelated to deno lint itself since you're still using eslint. An issue in Deno's main repo is probably a better place for compatibility issues with npm packages...

@justinfagnani would the proposed functionality in #185 solve your use cases?