Creating NPM Package with ReactJS

Creating NPM Package with ReactJS

CodeSweetly
This is a sample of the book's content.Buy on Leanpub

Table of Contents

Creating NPM Package with ReactJS

  • Introduction
    • Welcome to the World of NPM Packages!
    • Why This Book Will Help You
    • What You Will Build
    • Use the Right Tools
    • What You Should Know First
    • Got Questions?
    • Let’s Get Started!
  • Project Configuration
    • 1. Set Up Your System
    • 2. Create a Project Directory
    • 3. Create a package.json File
    • 4. Configure the Project as an ES Module NPM Package
    • 5. Initialize a Git Repository
    • 6. Specify the Files Git Should Ignore
    • 7. Stage and Commit Your Project’s Changes to Git
    • 8. Configure a GitHub Remote Repository
    • 9. Push Your Local Git Directory to the Remote Repo
    • 10. Install React
  • Testing React Component
    • 1. Install the Testing Tools
    • 2. Specify Vitest as Your Project’s Test Runner Tool
    • 3. Create Your Code Files
    • 4. Write Your Test Case
    • 5. Develop Your React Component
    • 6. Configure the Entry File
    • 7. Install the Code Compiler
    • 8. Configure Vite to Compile Your Code
    • 9. Configure Vitest’s Testing Environment
    • 10. Run the Test
  • Commit Message Configuration
    • Conventional Commits Message Syntax
    • Enforcing the Conventional Commits Format
    • Setting Up Husky
    • Creating a Hook to Auto-Lint Commit Messages
  • Setting Up Commitlint GitHub Action
    • 1. Create a Commitlint GitHub Action Workflow File
    • 2. Define the Commitlint GitHub Action Workflow
    • 3. Test the Commitlint GitHub Action Workflow
  • Styling React Components
    • 1. Create the Stylesheet
    • 2. Apply CSS Styles to Your Component
    • 3. Add the Stylesheet to the Entry File
    • 4. Run the Test
  • Compiling React to JavaScript
  • Distinguishing Source Code from Distribution Code
  • Defining Package’s Runtime Entry Points
  • Local Testing of Unpublished Package
    • 1. Link-Install Your Package Globally in Your System
    • 2. Create a NextJS Demo Website for Testing Your Package
    • 3. Install Your Package from Your System’s Global Folder to the Test-App
    • 4. Configure Turbopack to Resolve Symlinks
    • 5. Use the Link-Installed Package in Your Test-App
    • 6. Unlink Your Package from the Test-App
    • 7. Unlink Your Package from the Global Folder
  • Creating README
  • Creating LICENSE
  • Publishing Package to NPM
    • 1. Search Engine Optimization (SEO)
    • 2. Confirm That Your Package Have Passing Tests
    • 3. Compile Any Pending Code
    • 4. Stage and Commit Your Project’s Changes to Git
    • 5. Specify the Files You Want to Publish to NPM
    • 6. Confirm the Files NPM Will Publish
    • 7. Stage and Commit Any Recent Changes
    • 8. Push Your Local Git Directory to the Remote Repo
    • 9. Sign In or Sign Up on the NPM Website
    • 10. Log In to NPM via the Terminal
    • 11. Confirm If Your Package’s Name Is Available
    • 12. Publish Your Package!
  • Local Testing of the Published Package
    • 1. Install the Package
    • 2. Import the Package
    • 3. Run Your Local Server
  • Production Testing of the Published Package
    • 1. Stage and Commit Your Changes
    • 2. Set up a GitHub Remote Repository for Your Next.js Test App
    • 3. Push Your Local Git Directory to the Remote Repo
    • 4. Sign In or Create an Account on the Vercel Website
    • 5. Deploy Your Project to Vercel
    • 6. Test the Package on Your 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
    • 1. Create a Release GitHub Action Workflow File
    • 2. Define the Release GitHub Action Workflow
    • 3. How to Overwrite semantic-release’s Default Configurations
    • 4. Notify Developers That the Package Uses Automated Version Management
  • NPM Trusted Publishing Configuration
    • Add a New Feature
    • Update an Existing Feature
  • Automating GitHub Releases
    • Add the Preset Library to Your Release Workflow
    • Configure semantic-release to Automatically Publish the Package’s Release Notes
  • Modularizing JavaScript Codebase
    • 1. Identify Independent Elements
    • 2. Split the Elements You Want to Extract into Their Separate Modules
    • 3. Import the Extracted Elements into the TweetButton.jsx File
    • 4. Release the Latest Version of the Project
  • Epilogue
    • What’s Next?
    • One Last Favor
Creating NPM Package with ReactJS/Compiling React to JavaScript

Compiling React to JavaScript

https://leanpub.com/creating-npm-package-with-react-javascript

Up next

Distinguishing Source Code from Distribution Code

In this chapter

  • Compiling React to JavaScript