Npm run start fails after newly creation of package-lock.json in release 2.21.0

[msteffl]

Bug description

In release 2.21 After deleting the package-lock.json, starting with cleaned up node_modules and creating the package-lock.json "new" with npm install there are a lot of errors when trying to start the project with npm run start. Seems that they come from @paperbits/prosemirror/prosemirrorHtmlEditor.ts

So the package-lock.json seems not to be in sync with the package.lock.

Reproduction steps

1. Clone repository
2. Delete the package-lock.json
3. Run npm install
4. Run npm run start
5. See errors

Expected behavior

I would expect that if I create a new package-lock.json from the package.json the project will also run without errors.

Is your portal managed or self-hosted?

Self-hosted

Release tag or commit SHA (if using self-hosted version)

release 2.21

Environment

• Operating system: iOS
• Browser: Google Chrome, Safari
• Version: 106.0.5249.119

Additional context

Add any other context about the problem here, including screenshots.

[ghost]

@msteffl, thank you for opening this issue. We will triage it within the next few business days.

[jsorohova]

Hello @msteffl, thank you for reporting the issue. I was able to reproduce it and we will prioritize this. Thank you and sorry for inconveniences.