Chance

maintainers, I'm re-opening this incase you find merit in it. Please feel free to close.

The approach I took was to create a local application which runs `codegen.Generate`. This is rough but it'll give you an idea: ```go package main import ( "context" "embed" "flag"...

ts-loader has support for references: ```js const TsconfigPathsPlugin = require('tsconfig-paths-webpack-plugin') module.exports = { entry: './src/index.ts', mode: 'development', output: { filename: 'bundle.js', }, resolve: { extensions: ['.ts', '.tsx', '.js'], plugins: [new...

Also, thank you for the tool. Sorry I forgot to mention that in my issue. :)

You've done a great job! I'm not sure if it is your plugin or if I just got the option wrong.

Is there anything else that can be done to help object support along? I'd love to use diamond-types with prosemirror.

This definitely seems to solve the biggest issue of using Yjs with prosemirror, and that’s history. With yjs+prosemirror, the entire document state is replaced which is problematic for certain use...

Wow, that was an incredibly informative rabbit hole. I had never really put much thought into the complexities of async collab. So it seems that peritext, in its current form,...

@axe-me no problem. Thanks for publishing the package. I'm just going to roll with esbuild for that package. It makes more sense anyway. I figured I'd let you know, regardless.

This is achievable by calling `setup` directly: ```js const mongoSetup = require('@shelf/jest-mongodb/setup'); module.exports = async config => { await mongoSetup(); const url = process.env.MONGO_URL; if(url == null) { throw new...