Introduction
- Welcome to NPM Package!
- How This Book Can Help You
- The Roadmap
- Dependencies
- Prerequisite
- Questions and Comments
- Let’s Get It Started!
Project Configuration
- 1. Setting Up Your System
- 2. Creating a Project Directory
- 3. Creating a package.json File
- 4. Initializing a Git Repository
- 5. Specifying the Files Git Should Ignore
- 6. Staging and Committing Your Project’s Changes to Git
- 7. Configuring a GitHub Remote Repository
- 8. Uploading Your Local Git Directory to the Remote Repo
Testing JavaScript Code
- 1. Installing the Testing Tool
- 2. Specifying Jest as Your Project’s Test Runner Tool
- 3. Configuring Jest to Support ECMAScript Modules
- 4. Configuring Babel to Use the @babel/preset-env Preset
- 5. Configuring Jest’s Testing Environment
- 6. Creating Your Code Files
- 7. Writing Your Test Case
- 8. Developing Your JavaScript Code
- 9. Running the Test
Commit Message Configuration
- Conventional Commits Messages Syntax
- Enforcing the Conventional Commits Format
- Setting Up Husky
- Creating a Hook to Auto-Lint Commit Messages
Setting Up GitHub Action
- 1. Creating a GitHub Action Workflow File
- 2. Defining the GitHub Action Workflow
- 3. Testing the GitHub Action Workflow
Defining Package’s Entry Point
Local Testing of Unpublished Package
- Link-Install Your Package Globally in Your System
- Creating a Directory for the Demo Website
- Creating a package.json File
- Initializing a Git Repository
- Specifying the Files Git Should Ignore
- Installing Your Package from Your System’s Global Folder to the Test App
- Using the Link-Installed Package in the Test App
- Creating the Demo Website’s Homepage
- Styling the Demo Website’s Elements
- Installing the Parcel Build Tool
- Specifying Parcel as Your Website’s Development Server
- Unlinking Your Package from the Test App
- Unlinking Your Package from the Global Folder
Creating README
Creating LICENSE
Publishing Package to NPM
- 1. Search Engine Optimization (SEO)
- 2. Specify the Files You Want to Publish to NPM
- 3. Confirm the Files NPM Will Publish
- 4. Confirm That You Have Passing Tests
- 5. Stage and Commit Any Recent Changes
- 6. Push Your Local Git Directory to the Remote Repo
- 7. Sign In or Sign Up on the NPM Website
- 8. Log In to NPM via the Terminal
- 9. Confirm If Your Package’s Name Is Available
- 10. Publish Your Package!
Local Testing of the Published Package
- 1. Installing the Package
- 2. Importing the Package
- 3. Running Your Local Server
Production Testing of the Published Package
- 1. Staging and Committing Your Changes
- 2. Setting Up a GitHub Remote Repository for Your Demo Test App
- 3. Uploading Your Local Git Directory to the Remote Repo
- 4. Signing In or Signing Up on the Vercel Website
- 5. Deploying Your Project to Vercel’s Server
- 6. Testing the Package on the Live Demo Website
Updating Package’s Versions
- Example 1: Updating to a Patch Version
- Example 2: Updating to a Minor Version
- Example 3: Updating to a Major Version
Automating Version Management
- How to Release Your Package’s Latest Version
- How to Overwrite Release-It’s Default Configurations
- How Release-It Determines Your Package’s Latest Version
- How to Provide Release-It with a Recommended Version
Automating Changelog Management
Automating GitHub Releases
- 1. Getting a GitHub Personal Access Token
- 2. Copying the Generated Token
- 3. Creating a GitHub Environment Variable
- 4. Telling Release-It Your GitHub Token’s Name
- 5. Making the GitHub Secret Available Locally in Your Project
- 6. Preventing Git from Monitoring the Environment File
- 7. Installing the Plugin for Loading the .env File
- 8. Loading the .env File While Releasing Your Project’s Latest Version
- 9. Staging and Committing Your Changes
Epilogue
- What’s Next?
- One Last Favor