How to use a custom version of Tagify

Front End Components
#1

How can I use a custom version of Tagify or other JS scripts?

Wappler adds:

<script src="https://unpkg.com/@yaireo/tagify"></script>

to the page when I use Tagify for example.

If I change that to something like

<script src="https://unpkg.com/@yaireo/tagify@4.15.2"></script>

and save the page then Wappler appends

<script src="https://unpkg.com/@yaireo/tagify"></script>

to the head again so it’s loading the script twice - once the version I want and the latest version.

So how can I prevent Wappler from adding the script again on save?

#2

Wappler reads the code and populates the App Structure panel from it. Equally, it writes the code when needed, too. So I believe what’s happening is Wappler knows the Tagify script is needed, check for the existance of the required line but doesn’t see it as you’ve changed it. So it puts the line in.

I think a feature request is needed whereby the script path could be overriden if you want a different one. However, I suspect that feature won’t be approved because of the possible issues particularly with how the js integrates with the Wappler UI.

#3

Thanks! That makes sense, but if that’s a feature that won’t get approved, then I’ll need to find an alternative to Tagify since their latest version is often unstable and not usable for production.

#4

I’m not Wappler staff so please don’t think I have any say in what requests are approved :wink:

I would submit the request as you never know.

#5

I’m aware of that, sorry if it sounded different :slight_smile:

Yeah, will do. Thanks again!

1 Like