David Burles
David Burles
It's not actually a very good idea to publish packages with a single entry-point despite it being commonplace.
Passing in number 0 as a child would result in nothing being rendered. See test: https://github.com/dburles/vhtml/blob/88278a1fb47f93edb40e974ab4eaf6923169f4a4/test/vhtml.js#L169-L178
Suggestions: 1. The `exports` field shouldn't stripped from the published `package.json` and no `index.mjs` file is included. @n1ru4l I found that you raised this issue earlier, (though not sure why...
When running `meteor` outside of the project root, the package will fail to find `custom.semantic.json` and throw an 'ENOENT: no such file or directory' error.
The way 500 errors are currently handled is that exceptions are caught and GraphQL sends the literal error message back to the consumer in the error response, such as `"message":...
Hopefully it can be removed once https://github.com/meteor/meteor/issues/1769 gets through.
It would make sense to also check deprecated arguments.
A `subscription` query results in an error `TypeError: Cannot read properties of undefined (reading 'name')`, originating here: https://github.com/slicknode/graphql-query-complexity/blob/master/src/QueryComplexity.ts#L260. I am not sure if this is only failing because the server...