leerobert

@arnog what's your priorities in terms of fully specing out the MathJSON? Do you have a list of operation/rules you want to full be able to implement? I've been interested...

I think the behavior of the fn should be similar to the behavior I see in the `sympy` package... where `expr == expr.func(*expr.args)`... such that the fn is an abstract...

We ever fixing this or what? Annoying to have logs spammed.

Ok I made a quick little hack around until this issue is resolved... it's not the cleanest but at the end of each `api/endpoint.ts` file I put the following: ```...

To add some context, firefox works fine but Chrome does not.

I had to do a patch-package in pm2 via https://github.com/Unitech/pm2/issues/4360#issuecomment-1148869202 in order to make this work in digitalocean apps. This PR would be massive.

I just tried it myself: ``` extensions: [ "Bold", "Italic", "Strike", "Underline", "Code", "CodeBlock", "CodeBlockHighlight", "BulletList", "OrderedList", "ListItem", "TodoList", "HorizontalRule", "Table", "Link", // 'OTitle', // 'ODoc', "OParagraph", "OBlockquote", "OTodoItem", "OHeading",...

@VincentSC any chance you could be a little more specific with the full `docker-compose.yml` including the nginx-proxy configuration? Or maybe some kind of step by step? Did you not use...

I figured it out. Strict mode breaks the rendering: https://stackblitz.com/edit/nextjs-jj6w5b?file=next.config.js If you disable the strict mode then it renders fine. Perhaps just a note in the installation to be sure...

Issue still exists. This works when you introduce a simple inline node like: ``` import { mergeAttributes, Node } from '@tiptap/core'; export type ChunkOptions = { HTMLAttributes: Record; }; export...