Reference

Reporting issues

Learn how to report errors in your code components.
Private Beta

During the private beta, we want to help you resolve issues quickly. The most effective way to report problems is by sharing your component library. Follow the steps below to provide the information we need to assist you.

Issue: Library won’t share to Webflow

1

Enable debug mode

Add DEBUG=true to your .env file to get detailed error information:

.env
$DEBUG=true
2

Bundle your library

Bundle your library using the Webflow CLI command. This will generate a dist folder in the root of your project with your bundled library.

$npx webflow library bundle --public-path http://localhost:4000/

Note: The public path is required to serve your library.

3

Share your repository

Push your code to a private repository and share access with the Scaled Design team.

4

Zip your project (Optional)

Optionally, you can zip your project to share it with the Scaled Design team.

Do not include sensitive files and large folders

Do not include the node_modules folder, nor your .env file or any other sensitive files.

5

Submit feedback

Submit your feedback through the Slack workflow in the #ext-beta-code-components channel, including:

  • Repository link / zip file
  • Any error messages from the bundle command
  • Steps you’ve already tried

Issue: Components aren’t rendering correctly in Webflow

1

Disable minification

Use development mode in Webpack to get readable error messages:

webpack.webflow.js
1module.exports = {
2   mode: "development",
3};
2

Share your library

Share a new version of your library and install it on your test site:

$npx webflow library share
3

Check browser console

Open your browser console and copy any error messages or warnings.

4

Share your repository

Push your code to a private repository and share access with the Scaled Design team.

5

Zip your project (Optional)

Optionally, you can zip your project to share it with the Scaled Design team.

Do not include sensitive files and large folders

Do not include the node_modules folder, nor your .env file or any other sensitive files.

6

Submit feedback

Submit your feedback through the Slack workflow in the #ext-beta-code-components channel, including:

  • Repository link / zip file
  • Browser console errors
  • Steps you’ve already tried
  • Additional context:
    • Are other Code Component Libraries installed on the site?
    • Did components work before but stopped after code changes?
    • Did components work before but stopped after CLI updates?
    • Are components rendering partially (content shows but styles don’t)?