basset & unpkg.com

[blondie63]

For a few days now, but not all the time during the day, my Laravel + Backpack v6 apps are very slow and I see that the browser is waiting for responses from unpkg.com
I see that on ./vendor all basset commands use unpkg.com

Why ?
Does this happen to others ?
Solutions ?

Thanks for help

[backpack-ai-bot[bot]]

This issue is related to Backpack and its use of Basset for asset management. Let me address your concerns based on the information provided in the knowledge sources.

1. Basset and unpkg.com usage:
   Backpack v6 introduced Basset, a new way to load CSS and JS assets Release Notes. Basset uses CDNs like unpkg.com to fetch assets, but it's designed to internalize these assets to improve performance and reliability.

2. Slow responses from unpkg.com:
   The slow responses you're experiencing are not unique. Other users have reported similar issues with CDN-based assets Github Issue.

3. Why this happens:
   This can occur due to various reasons, including CDN outages or slow responses. It's especially noticeable when assets are not cached locally.

4. Solutions:

   a. Cache assets locally:
   Run php artisan basset:cache to cache all CSS and JS assets locally. This should significantly improve load times Upgrade Guide.

   b. Enable development mode:
   If you're actively developing and need to bypass Basset caching, add BASSET_DEV_MODE=true to your .ENV file Upgrade Guide.

   c. Check for Basset issues:
   Run php artisan basset:check to identify and resolve any Basset-related issues Github Issue.

   d. Ensure correct APP_URL:
   Make sure your APP_URL in the .env file is correctly set Github Issue.

   e. Update Backpack:
   Ensure you're using the latest version of Backpack, as recent updates have addressed some Basset-related issues Github Issue.

If these solutions don't resolve the issue, you may need to open a new issue on the Backpack GitHub repository for further assistance.

Relevant sources:

Github Issue (closed): [HAS-FIX] ASSETS NOT LOADING FROM CDNS - 12-04-2024
Github Issue (closed): [Bug][v6.x] https error
Release Notes|Basset - a better way to load CSS and JS assets
Github Issue (closed): [Bug] CSS not loaded when pushed on production
Upgrade Guide|CSS & JS Assets
Github Issue (closed): [4.0][Feature][Proposal] Remove dependency on CDNs - make Backpack work offline
Github Issue (closed): How can I download all dependency?
Github Issue (closed): [4.0][Feature][Proposal] Remove dependency on CDNs - make Backpack work offline
Upgrade Guide|Cache
Github Issue (closed): [4.0][Feature][Proposal] Remove dependency on CDNs - make Backpack work offline

[blondie63]

I've checked all points but the issue is still here !!
Why app call many times unpkg.com where basset is right configured ??

[karandatwani92]

Hey @blondie63

Can you add BASSET_DEV_MODE=false to your env and run php artisan basset:cache?
This will force the app to cache the assets locally and server from the local cache.

[blondie63]

Now it's ok but it's strange that problem come only in last days..
Thanks

[yurik94]

Still slow, can we have an option to switch between another CDN service or to self host those files?

[blondie63]

I've same problems but only locally on my mac, same code on dev server is fast !

what could it be?

[blondie63]

@tabacitu @yurik94
I tried a thousand times and I discovered that the problem is definitely related to Basset and unpkg.com!
But if in my local .env I put app_env=production then everything works quickly!
The strange thing is that until a few days ago it didn't do this!!
What could it be?

[yurik94]

Hello Mauro @blondie63

The problem is vey simple, the unpkg.com CDN is down/experiencing problems since a few days.

Status: https://unpkg.com/status

As you can see from chrome devtools, some assets are loaded and some others are very slow to download/fail completely, probably because of CloudFlare trying to reach the origin server of unpkg.com which is down.

Since backpack is heavily relying on unpkg.com, which has a pretty bad reputation, I think that it should be changed with jsDeliver.

You can resolve temporarily by invoking: sail artisan basset:cache
With this command all of the bassets will be copied and served locally.

Basset is disabled by default on local environment. If you want to change it, please set BASSET_DEV_MODE=false in your env file.

So you also need to put BASSET_DEV_MODE=true BASSET_DEV_MODE=false in your local .env

[yurik94]

Sorry, errata corrige:

BASSET_DEV_MODE=false

enable/disable dev mode using BASSET_DEV_MODE=false - this will force Basset to internalize assets even on localhost

[tabacitu]

Yeah... this is really unfortunate... unpkg has really let us down here.mFor the moment, while they're having problems, that solution will work.

In the next version, due to launch in a few weeks, we've already removed most unpkg links and we've provided a way to manually change the url to whatever you like, if the CDN proves unreliable.

But until then... BASSET_DEV_MODE=false will help.

[munjaldevelopment]

Getting internal server error on jquery unpkg.com. Facing issue on few projects due to this.