Joel

I fixed this via https://jestjs.io/docs/manual-mocks#mocking-node-modules *Note my jest config includes `roots: ["/jest"]` `jest/__mocks__/@formkit/auto-animate/react.js ` ``` const useAutoAnimate = () => [null]; export { useAutoAnimate }; ```

Im doing this for now - on EditorProvider editorProps={{ attributes: { ...(props.autoFocus ? { autofocus: "true" } : {}), }, }}

thanks for raising, thought i was going mad for anyone else seeing this, here is my workaround https://github.com/ueberdosis/tiptap/pull/4579#issuecomment-2087132599

experiencing the same with EditorProvider, I'm happy to open a PR making children optional? @bdbch draft [here](https://github.com/ueberdosis/tiptap/pull/5102)

Ran into this issue today, until this or another fix is merged - my current workaround is like this ``` {/* due to https://github.com/ueberdosis/tiptap/pull/4579 editor is null on initial render...

@patrickedqvist @MarkLyck @nc How do you see this being done? I see 2 things that could be nice 1. The ability to specify multiple environments, the action checks on each...

> @pip8786 How did you find the name of the environment? I am creating a preview deployment with `testing` branch so I tried: "Preview - testing", "testing" and "Preview", but...

Looks great @NotWoods 🚀 Do you think we'd need a separate rule for enforcing `StoryObj` instead of `StoryObj` to get full safety? (thats the only way I can get TS...