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
{{ message }}
This repository has been archived by the owner on Apr 29, 2021. It is now read-only.
I have a project that still uses v3.4.0 of this plugin which still makes use of the prefix option. The project uses a global instance of IncrementalDOM that is slightly modified from it's original state. Because of this our project isn't currently compatible with the newer moduleSource option, and it doesn't make sense to try and refactor at this point.
My question is, is there any way to replicate the old behavior of prefix with the latest release of this plugin?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have a project that still uses v3.4.0 of this plugin which still makes use of the
prefix
option. The project uses a global instance of IncrementalDOM that is slightly modified from it's original state. Because of this our project isn't currently compatible with the newermoduleSource
option, and it doesn't make sense to try and refactor at this point.My question is, is there any way to replicate the old behavior of
prefix
with the latest release of this plugin?The text was updated successfully, but these errors were encountered: