Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with Integrating Custom Component into FormEditor in a Vue.js + TS + Vite Environment #1104

Open
EinArlyn opened this issue Mar 24, 2024 · 0 comments
Assignees
Labels
backlog Queued in backlog bug Something isn't working

Comments

@EinArlyn
Copy link

I encountered issues while following the instructions to create custom components for FormEditor, leading me to raise an issue where I was advised to use Webpack for the build process. Taking this advice, I set up a project with Vue.js, TypeScript, and Webpack, and successfully implemented a custom component, guided by this example.

After a successful implementation in the test environment, I attempted to transfer the functionality to the main project that uses Vue.js + TS + Vite. In this environment, I encountered a problem: errors occur when dragging the component into FormEditor.

The problematic console errors are as follows:

Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'context')
at index.js:344:19

Uncaught TypeError: Cannot read properties of undefined (reading 'addEventListener')
at Object... (index.esm.js:62:1)

Steps to Reproduce:

  1. Clone the project.
  2. Install dependencies and run the project.
  3. Drag the custom component into the form editor.

Expected Behavior:

The custom component should integrate seamlessly into FormEditor without any errors.

Actual Behavior:
The component does not integrate, and errors are displayed in the console.

Question:
How can the functionality of the custom component, which works in an environment with Webpack, be correctly transferred to a project on Vue.js + TS + Vite?

Additional Information:

image

Any help or debugging suggestions would be greatly appreciated.

@EinArlyn EinArlyn added the bug Something isn't working label Mar 24, 2024
@Skaiir Skaiir self-assigned this May 29, 2024
@Skaiir Skaiir added the backlog Queued in backlog label May 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog Queued in backlog bug Something isn't working
Development

No branches or pull requests

2 participants