fix: component resolver issue if component not present in config

[sagarchoudhary96]

Fixes #339

[vercel]

@sagarchoudhary96 is attempting to deploy a commit to the Measured Team on Vercel.

A member of the Team first needs to authorize it.

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
puck-demo	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 25, 2024 10:53am
puck-docs	✅ Ready (Inspect)	Visit Preview		Jan 25, 2024 10:53am

[sagarchoudhary96]

@chrisvxd this fixes it.

[chrisvxd]

Makes sense! Sounds like you have an out-of-date data payload, but there's no harm in us checking within Puck, too.

Thanks for the fix.

[sagarchoudhary96]

so actually, the use case we use puck editor is to build pages and those can be built through automations etc too, and what might happen is we might have added some new components to those pages through one flow but didn't have added support yet to the puck editor and hence this could happen when opening those pages in puck editor.

[chrisvxd]

Interesting use case @sagarchoudhary96! Can you share more about your project?

[sagarchoudhary96]

we basically use some automations in place to generate these custom pages for each of our user based on their answers , and then these pages are available to other team members to be able to easily edit/update accordingly as per any additional changes needed using the editor interface made using puck editor.