Dobes Vandermeer

Pasting `\begin{multiline} ... \end{multiline}` into a mathlive input doesn't work right now on the website or the latest npm version, FWIW.

One use case for this would be if I want to show a user interface to allow the user to set overrides manually when testing. The UI could show the...

I've been working on a prototype of this in here: https://github.com/dobesv/planout-ts/blob/master/src/PlanOutParameterGatherer.ts Just in case anyone is interested, maybe we can collaborate.

The way the `babel-plugin-import-graphql` works is that it replaces the import with a variable with the imported data. By the time this plugin sees that variables, it doesn't appear to...

Yes, that would make sense. However, once `babel-plugin-module-resolver` sees the graphql import, it's not an import any more. `babel-plugin-import-graphql` takes something like: ``` import query from './query.graphql'; ``` And replaces...

The module resolver doesn't know how to parse and modify graphql files, though. So it can't process the graphql file before the graphql plugin runs. It helps resolve the path...

OK, I investigated this some more, and I found that the npm distribution is inlining prop-types into the module source code. This inlined version of prop-types always prints that error....

It should probably be deployed with a dependency or peer dependency on prop-types and not embed prop-types into the js file.

Middleware doesn't call `next` if it handles the request. This is the case here. This isn't a bug. Otherwise it would call `next` and the next handler would return `404...

It will call `next` if you set it up to only proxy certain paths, and the request doesn't match one of those paths.