Hyeseong Kim

I'm using a similar as @AArnott does, with a simple plugin for using `yarn up` with more controls https://github.com/cometkim/yarn-plugin-bump

Just curious, what is the main reason for converting syntax?

I'm thinking of a PPX syntax that can be introduced without breaking changes. ex) ```res @tagged(nodeName) type rec node = | Text({ nodeName: [#"#text"], value: string, }) | H1({ nodeName:...

And there are few more; apollo-link-context also doesn't have peerDeps. I can't use apollo with yarn 2 because of this. Any plan to update?

Thanks @christopher-caldwell , but, my library has zero dependencies 😅

Without adding a new key it can be expanded as string | { input, output }. I'd like to make a PR for this. Is there any other discussion I...

before: 17.23kB minified after: 17.26kB minified

@LexSwed Oh thanks, I've never noticed that I expect the API only change element, do not composing styles. for example: ```ts const ButtonLink = Button.as(Link); // only use Button's style...

Hi @impulse. Yes, this plugin was changed in v1.0, to generate code for queries that actually using by Gatsby instead of directory globs. So, if you didn't call `createPage` action...

> Will the solution you described here solve this? I think the culprit is that I still use tsnode and didn't make the switch to it yet. @impulse Unfortunately, It...