Andreas Lind
Andreas Lind
Maybe we could use [the `browser` field](https://github.com/defunctzombie/package-browser-field-spec) to point to the right location?
Yeah, I think we should specify `browser` no matter what, I don't think there'd be any downside to that. Isn't it pretty much the same, though? If these browser tests...
@mwoc Unfortunately that subscription only fires when the contents of the previously bound observable array changes, but not at the moment when the `foreach` expression evaluates to a different observable...
@bramstein Absolutely: https://github.com/bramstein/knockout.selection/pull/25
I ended up working around the bug by wrapping my view in a `with` binding: ``` html ... ``` Would still be nice to get this fixed, of course.
Hmm, wouldn't that make EventMatcher a totally generic pattern matching module? Sounds like we'd immediately build an abstraction on top of it that saves us from checking for the presence...
Okay, that makes me feel slightly less worried about hardcoding them. Still, I think it would be worth it to expose them as a pure DX/discoverability thing?
I just tried to upgrade to 1.1.0, and the `.mjs` extension in the transpiled code is causing a bit of trouble in my app: ``` import { ValidationContext, isCompositeType, TypeInfo,...
@ivome, but don't you agree that _something_ is wrong with the builds? Right now when I use vanilla `import`s in my node.js project: ```js import { GraphQLObjectType } from 'graphql';...