-
|
Seeing as this UI kit is based on frontend framework Bootstrap and there are CDN links in the docs to the JS/CSS assets, why would a packager manager like npm be desirable/needed/available for client-side tabler? As I understood, npm isn't really built for frontend development and tabler is a client-side-running frontend UI kit? The founder is a graphic designer, right; which makes me wonder more why server-side-JavaScript-originating npm would come into play? Is there some advantage to using tabler with npm+parcel for example? Over unpkg CDN? Forgive my noob ignorance! This UI kit is literally amazing. I can't wait to use it and I hope to become a sponsor too. It reminds me of legacy SB Admin v2 for Bootstrap 3. I know this is probably a dumb question, so be kind 🙃 |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
It's a reasonable question. I suppose it's just easier for there to be one package manager for all things JavaScript/TS, rather than adding an alternative for client side code. Since all the code running on the client side has to start out as data on the server side at some point, I don't see how there would be any advantages to having a specifically client side package manager. Can you? Also, there are plenty of really good reasons not to use public CDNs, especially for production level websites. |
Beta Was this translation helpful? Give feedback.
-
|
Using NPM for installing Tabler allow me to build a very specific JS bundle with webpack. I only choose what I need from the library and webpack includes only this code to the final build. Using the CDN is downloading the whole library to the client side. NPM is useless on the final client side for sure, but very useful for developers in the development or building processes. |
Beta Was this translation helpful? Give feedback.
It's a reasonable question. I suppose it's just easier for there to be one package manager for all things JavaScript/TS, rather than adding an alternative for client side code. Since all the code running on the client side has to start out as data on the server side at some point, I don't see how there would be any advantages to having a specifically client side package manager. Can you? Also, there are plenty of really good reasons not to use public CDNs, especially for production level websites.