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
A. 🔴 Remove the need for symlink by saving the files in the public folder (public/bassets), GIT IGNORED:
PROS:
Easier to install: No need to create a symlink.
Easier to develop: You run php artisan basset:cache on install, then have the assets (no more DEV_MODE);
CONS: none
B. 🔴🟡 File map/manifesto to easily track file versions across multiple files
C. 🟡 In airgapped servers, we have no support for files with variables (eg. multiple languages: select2/en/select2.js, select2/pt/select2.js) - basically add support for @basset('http://example.com/select2.'.$lang.'.js', ['lang' => ['en', 'ro', 'pt', 'it']])
D. 🟡⁉️ Deprecate zips, load the files directly from http://raw.github.com/someone/somerepo/tag/1.2.3/asset.js
E. 🔴 eliminate DEV_MODE - the different behaviour in local/staging/production is causing more trouble than it's worth
--
ALSO TO DO:
F. 🔴 Remember assets in git (do NOT gitignore public/bassets):
PROS:
Faster deployments: No need to run php artisan basset:cache on deploy;
Safer deployments: If CDN is down during deployment, no problem;
Easier to install: No need to create a symlink.
Easier to develop: You run php artisan basset:cache on install, then have the assets (no more DEV_MODE);
CONS:
Big git repo size: All the CSS and JS assets will be commited to repo, whether you use them or not; ✅
Dirty commits: Every time you run php artisan basset:refresh on local, you override the changed CSS and JS files => dirty diffs; ⚠️
Dirty repo in staging/prod: If an asset has NOT been internalized in local, it will be internalized in staging/prod and dirty that repo; possibly preventing the next deployment; ⚠️
DON'T DO:
G. ⚫ Do not "cache" @bassetBlocks, they are already on the page, no need to put them on a file to get an additional file
--
LET'S NOT TALK ABOUT IT:
🟡 Create a way to don't push not used assets (eg: if you don't use select2, don't push it).
🔵 no easy way to update assets used (no php artisan basset:update)
🔵 no easy way to get notified when an asset has security issues
TODO:
public/bassets
), GIT IGNORED:php artisan basset:cache
on install, then have the assets (no more DEV_MODE);@basset('http://example.com/select2.'.$lang.'.js', ['lang' => ['en', 'ro', 'pt', 'it']])
http://raw.github.com/someone/somerepo/tag/1.2.3/asset.js
--
ALSO TO DO:
public/bassets
):php artisan basset:cache
on deploy;php artisan basset:cache
on install, then have the assets (no more DEV_MODE);php artisan basset:refresh
on local, you override the changed CSS and JS files => dirty diffs;DON'T DO:
--
LET'S NOT TALK ABOUT IT:
php artisan basset:update
)Examples:
The text was updated successfully, but these errors were encountered: