You don’t “need” a component library, it can be rather useful and beneficial.
Here are some points I would like to mention:
You don’t use component libraries only for components that are shared between projects. We can also build component libraries for other developers to use in their own projects, which is what we call “open source”, one of the main reasons why we have npmjs, for example.
Team collaboration is another advantage of a component library, because you can share your component with your team mates. Working in projects is not always an egocentric and independent craft, it is a teamwork effort.
Pre-build components also have the advantage of being better-performant, which leads to faster load times, which at the end of the day benefits the user experience.
Building a component library has more benefits, these are some of the main points I believe are important when it comes to building an NPM library.
Whether exposed to the outside-world (as an node package) or not, is not the issue.
This article doesn't deal with the "need"/"reason" but the "how".
More developers don't know how to even start making a components "library" because they are so focused on the day-to-day tasks which are just tiny pieces of a big puzzle (most) never really understand (yet) or ever wish to understand.
I've met many front-end developers in my (almost 20 years) career and maybe 1% will even obtain the ability to really build a library, as they are clueless about the tooling and how it's all connected.
The author mentioned “need”, hence why I said it. It is not a must, but it’s a great tool to have in one’s belt.
I think building component libraries should become a skill taught in courses, bootcamps and also part of the curriculum in software engineering degrees - which I’m not exactly sure if they already do, because I’m in CS, but if they haven’t included this topic, in my opinion, they should.
The thing with building libraries is the configuration, which I believe is the “trickiest” to learn how to setup, particularly in TypeScript, for those who use it. But, the outcomes are great!
Besides, building libraries and publishing on NPM is loads of fun, particularly when you go and see the downloads rising 🙃
I think that one other important thing to keep in mind when it comes to building component libraries is the fact that some of the existing libraries are outdated or don’t work well with certain versions of a framework, let’s say Vue 2 and 3, for example. It is also important to look for a “niche”, something that nobody explored yet or that is still very much untouched.
At the end of the day, it all comes down to the ambition of the developer and the needs for a particular project, as well as the demand for a particular library.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
You don’t “need” a component library, it can be rather useful and beneficial.
Here are some points I would like to mention:
You don’t use component libraries only for components that are shared between projects. We can also build component libraries for other developers to use in their own projects, which is what we call “open source”, one of the main reasons why we have npmjs, for example.
Team collaboration is another advantage of a component library, because you can share your component with your team mates. Working in projects is not always an egocentric and independent craft, it is a teamwork effort.
Pre-build components also have the advantage of being better-performant, which leads to faster load times, which at the end of the day benefits the user experience.
Building a component library has more benefits, these are some of the main points I believe are important when it comes to building an NPM library.
Whether exposed to the outside-world (as an node package) or not, is not the issue.
This article doesn't deal with the "need"/"reason" but the "how".
More developers don't know how to even start making a components "library" because they are so focused on the day-to-day tasks which are just tiny pieces of a big puzzle (most) never really understand (yet) or ever wish to understand.
I've met many front-end developers in my (almost 20 years) career and maybe 1% will even obtain the ability to really build a library, as they are clueless about the tooling and how it's all connected.
You have made great points!
The author mentioned “need”, hence why I said it. It is not a must, but it’s a great tool to have in one’s belt.
I think building component libraries should become a skill taught in courses, bootcamps and also part of the curriculum in software engineering degrees - which I’m not exactly sure if they already do, because I’m in CS, but if they haven’t included this topic, in my opinion, they should.
The thing with building libraries is the configuration, which I believe is the “trickiest” to learn how to setup, particularly in TypeScript, for those who use it. But, the outcomes are great!
Besides, building libraries and publishing on NPM is loads of fun, particularly when you go and see the downloads rising 🙃
I think that one other important thing to keep in mind when it comes to building component libraries is the fact that some of the existing libraries are outdated or don’t work well with certain versions of a framework, let’s say Vue 2 and 3, for example. It is also important to look for a “niche”, something that nobody explored yet or that is still very much untouched.
At the end of the day, it all comes down to the ambition of the developer and the needs for a particular project, as well as the demand for a particular library.