Replies: 1 comment 11 replies
-
The cdn link would override the Alpine window instance (or vice versa). Why do you need two on the page? But to differentiate, you'd need to just always use your imported one (or passed to the plugin functions the one you want applied) |
Beta Was this translation helpful? Give feedback.
11 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
So I have a page with a traditional build of Alpine and one built with a prefix.
I have a Alpine.store that works just fine when the prefixed version in on page alone. But when I add the traditional build to the page, I can no longer access the store data.
For example I am using code like this that can no longer see. the "items" ...
Alpine.store("formsnap").items.forEach((item) => { ... });
Is there a special way to target the "Alpine" instance using the prefix?
Or should I import the prefixed version. in with different name like so ...
import prefixedAlpine from "alpinejs";
Thanks to any help folks can give.
Beta Was this translation helpful? Give feedback.
All reactions