You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I attempted to implement a dynamic select and found that I could not do so when also using a relative import. After removing the import (and all references to it), the dynamic select works as expected (in Bun)
Interestingly, it works correctly from the "deployed" page, just not the editor page:
This is using TS/Bun. I tried it with Deno and neither worked. The error popup in Deno was a similar message about not being able to find the import.
Whether bundles are enabled or disabled seemed to have no effect.
To reproduce
Attempt to use dynamic select in a script that also has a relative import.
Expected behavior
Dynamic select should work even with imports.
Screenshots
No response
Browser information
No response
Application version
EE v1.393.2-2-g6f0af6b8c
Additional Context
No response
The text was updated successfully, but these errors were encountered:
I should add: obviously in my example, the dynamic select values aren't actually "dynamic". This was a test to see if I could get it working before making the values dynamic.
Describe the bug
I attempted to implement a dynamic select and found that I could not do so when also using a relative import. After removing the import (and all references to it), the dynamic select works as expected (in Bun)
Interestingly, it works correctly from the "deployed" page, just not the editor page:
This is using TS/Bun. I tried it with Deno and neither worked. The error popup in Deno was a similar message about not being able to find the import.
Whether bundles are enabled or disabled seemed to have no effect.
To reproduce
Attempt to use dynamic select in a script that also has a relative import.
Expected behavior
Dynamic select should work even with imports.
Screenshots
No response
Browser information
No response
Application version
EE v1.393.2-2-g6f0af6b8c
Additional Context
No response
The text was updated successfully, but these errors were encountered: