While I try to make myself clear when explaining things in this course, if you need a top-up of some of the terminology, feel free to return to this page.
If there are other phrases you don’t understand, then drop a message in the Discord, and I’ll go ahead and update this list.
Library Consumers
The developers who use component libraries in their own projects. That project might be a web application, or it may even be another component library.
End Users
These are the web users who end up interacting with the user interfaces over the web.
Component Library
A cohesive group of components and utilities that share a purpose (functional or visual) that other developers can consume in their projects.
JavaScript Package
A JavaScript package is a file or folder that has an associated package.json file. It could be a single function or an entire collection of components. If you run npm install <package-name> in your project, then you’ve used someone else’s package in your project.
Package Registry
A database of packages that are hosted by a company. If you’re developing JavaScript code, you’re most likely to interact with the NPM registry. When publishing your packages for public consumption, you’ll publish them to the NPM registry. Other members of the web development community will be able to download your package from the NPM registry to use in thei