npm is like a giant library of code building blocks. There are tons of these “blocks”, aka “packages” that we can compose together to build cool things. We can use packages by other developers, but we can also write and publish our own.
In this course we will learn how to create, publish, and update our own packages. We will create a JavaScript utility module to filter out sensitive words from a string, including tests and development file watching. We will then cover publishing and updating our package. This same approach can be used to create and publish other types of packages too like components (React, Angular, Web Components etc.) and command line interfaces.
A Community Resource means that it’s free to access for all. The instructor of this lesson requested it to be open to the public.
I liked a lot. To be perfect for me would be missing just how to handle typescript
good explained the step by step - thanks
The instructions are somewhat outdated because of changes in the software being used. E.g. Babel has been re-structured in version 7 and we now need to say: npm install --save-dev @babel/core @babel/cli @babel/preset-env
Start with a short background about npm. explaining more about why we do each thing, like build and test..
Structure-wise, it's really good because it has a focus on publishing the package. Would be nice if :
1 - author can add a few gotchas that could happen when publishing an npm package. For example, package name can't be the same, and the usage of "@namespace/some-package" is exclusive to paid account.
2- author can revise the content. In particular, the babel dependencies are really outdated and since the time this course was first published, there have been many ways of configuring a project.
was very helpful! i hope there are more npm courses in the future
A Community Resource means that it’s free to access for all. The instructor of this lesson requested it to be open to the public.