tiptap: Bug with build project after release v2.0.0-beta.212 (lodash/debounce issue)

It would be beneficial to move away from semver (^2.0.0 equals to 2.X.X) which essentially leads to your own pinning of each extension being ignored

We’re also seeing the above lodash issue. Even when pinning to 213 (like "@tiptap/react": "2.0.0-beta.213" - without the ^) , Tiptap will still install at @tiptap/extension-bubble-menu at 2.0.0-beta.215, which for us, has the lodash issue.

We managed to temporarily (using Yarn) get around this by adding a resolution to package.json, which makes sure that no newer version of @tiptap/extension-bubble-menu will get installed.

"resolutions": {
    "@tiptap/extension-bubble-menu": "2.0.0-beta.213"
}

Would be great to find out what’s causing it on the newer builds though.

Thanks for trying out @ram-you - if some more people could verify that it’s working again on 217 would be great!

can’t work with tiptap since 209, the build crashes because of this lodash. The most intresting thing - I am not even using this bubble menu. It is just included in tiptap/vue package by default

I’ll release a fix asap

beta 217 does the trick for us, thanks!

Hi @bdbch , Have updated to beta.215 but still have error:

Named export 'debounce' not found. The requested module 'lodash' is a CommonJS module, which may not support all module.exports as named exports. CommonJS modules can always be imported via the default export, for example using: import pkg from 'lodash'; const { debounce } = pkg;

Occurs only when refresh page (server side rendering) .

@bdbch I have the same error. I try to use 209-216 versions but always get the error:

ERROR in ./node_modules/@tiptap/extension-bubble-menu/dist/index.js 3:0-39
Module not found: Error: Can't resolve 'lodash/debounce' in '/Users/<user>/.../node_modules/@tiptap/extension-bubble-menu/dist'
Did you mean 'debounce.js'?
BREAKING CHANGE: The request 'lodash/debounce' failed to resolve only because it was resolved as fully specified
(probably because the origin is strict EcmaScript Module, e. g. a module with javascript mimetype, a '*.mjs' file, or a '*.js' file where the package.json contains '"type": "module"').
The extension in the request is mandatory for it to be fully specified.
Add the extension to the request.

I need to release my app later today but I can’t even do a build as it always crashes on this error. Which older version can I still try to use so that my code works and the build does not crash?

Hi @bdbch , I’m also seeing this error in the next js after updating to beta.215.

Hey guys. Sorry for the inconvenience. I released a quick fix (beta.213) - would be nice if you could see if that works out for you.

Still unable to use the module. Getting this error on 216.

Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/<project>/node_modules/lodash/debounce' imported from /<project>/ttp-website/apps/backend/node_modules/@tiptap/extension-bubble-menu/dist/index.js
Did you mean to import lodash/debounce.js?

Same for me and it’s terrible. Didn’t expect that there is no stable version in the releases 😃

beta.216 still doesn’t let the react-admin simple example compile (see https://github.com/marmelab/react-admin/pull/8622#issuecomment-1423008220 for details)

Hi @bdbch , Have updated to beta.216 but have now an another error, this time the error message is:

Cannot find module '/.output/server/node_modules/lodash/debounce' 
imported from /.output/server/node_modules/@tiptap/extension-bubble-menu/dist/index.js

Did you mean to import lodash/debounce.js?

The error occurs only when refresh page (server side rendering on NUXT), and when I put the component inside client-only, the error disappear:

 <client-only> 
   <tiptapEditor  />
 </client-only> 

Thank you.

@timheerwagen Just pushed another fix (beta.215) which should fix this issue

Installing with npm install --save @tiptap/react @tiptap/pm @tiptap/starter-kit with the new 2.0.0-beta.213 resolved the Lodash import issue for me.

In my tests i have following error now:

Details:

    /home/runner/work/design-system/design-system/node_modules/lodash-es/lodash.js:10
    export { default as add } from './add.js';
    ^^^^^^

    SyntaxError: Unexpected token 'export'

      2 | import Placeholder from "@tiptap/extension-placeholder";
      3 | import Underline from "@tiptap/extension-underline";
    > 4 | import { EditorContent, useEditor } from "@tiptap/react";
        | ^
      5 | import StarterKit from "@tiptap/starter-kit";
      6 | import cn from "classnames";
      7 | import { useState } from "react";

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:[159](https://github.com/Neuvernetzung/design-system/actions/runs/4112161964/jobs/7096752133#step:9:160)8:14)
      at Object.<anonymous> (node_modules/@tiptap/extension-bubble-menu/dist/index.cjs:11:17)
      at Object.<anonymous> (node_modules/@tiptap/react/dist/index.cjs:2:28)
      at Object.<anonymous> (src/components/ui/RichText/richText.tsx:4:1)
      at Object.<anonymous> (src/components/ui/RichText/index.ts:2:1)
      at Object.<anonymous> (src/components/ui/RichText/richText.test.tsx:2:1)


Test Suites: 1 failed, 28 passed, 29 total

This may also be related to this update.

can someone revert this buggy commit, please

I’ll close this issue for now. If anyone still has problems feel free to reopen or open a new ticket if it’s a new build issue.

Thanks

no wayy its not working again on v2.0.0-beta.216

Hi @zakkempson, I managed it using:

"resolutions": {
    "@tiptap/extension-bubble-menu": "2.0.0-beta.209"
}

Because 213 version does not work for me. I am using NextJS 13.1.6, Typescript 4.9.5 and NodeJS 18.12.1 (LTS)

@nephew92 problem with resolve internal package solve as add package to package.json

"@tiptap/pm": "^2.0.0-beta.212",

or install manualy

npm i --save @tiptap/pm

but question with lodash/debounce is open