Skip to content

[lexical-examples] Bug Fix: missing dependency @lexical/utils at examples/react-rich-collab#7743

Merged
etrepum merged 1 commit intofacebook:mainfrom
debuggingfuture:main
Aug 7, 2025
Merged

[lexical-examples] Bug Fix: missing dependency @lexical/utils at examples/react-rich-collab#7743
etrepum merged 1 commit intofacebook:mainfrom
debuggingfuture:main

Conversation

@debuggingfuture
Copy link
Copy Markdown
Contributor

@debuggingfuture debuggingfuture commented Aug 7, 2025

Description

Expected vs Actual

  • npm i && npm run dev run out of the box
  • however below error is thrown
11:55:27 PM [vite] Internal server error: Failed to resolve import "@lexical/utils" from "src/plugins/ToolbarPlugin.tsx". Does the file exist?

Root Cause & Changes

  • package-lock.json is outdated, adding @lexical/utils in package.json and npm i resolves the issue
  • seems other packages also has outdated package-lock.json. Shall we bump all of them & run npm i at build process everytime?

Test plan

After

  • tested npm i && npm run dev able to start

@vercel
Copy link
Copy Markdown

vercel bot commented Aug 7, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
lexical ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 7, 2025 3:10pm
lexical-playground ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 7, 2025 3:10pm

@meta-cla
Copy link
Copy Markdown

meta-cla bot commented Aug 7, 2025

Hi @debuggingfuture!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

@meta-cla
Copy link
Copy Markdown

meta-cla bot commented Aug 7, 2025

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

@meta-cla meta-cla bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Aug 7, 2025
@etrepum
Copy link
Copy Markdown
Collaborator

etrepum commented Aug 7, 2025

The examples are not part of the build toolchain so these sorts of things can fall through the cracks

@etrepum
Copy link
Copy Markdown
Collaborator

etrepum commented Aug 7, 2025

There's also a bit of a bootstrapping issue with the package-lock files for the examples because they can't be updated (in any conventional way) until after the new version is published to npm

@etrepum etrepum added this pull request to the merge queue Aug 7, 2025
Merged via the queue into facebook:main with commit c8a365f Aug 7, 2025
36 of 37 checks passed
@etrepum etrepum mentioned this pull request Aug 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants