npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

@fynd-design-engineering/fynd-one-v2

v3.4.1

Published

Updated CDN for fynd.com

Readme

Fynd one CDN

All custom code used in fynd one project

✨ Features

  • 🔧 Modern TypeScript Setup - Full TypeScript support with strict type checking
  • ⚡ Lightning Fast Builds - Powered by esbuild for instant compilation
  • 🔄 Live Development - Hot reloading for instant feedback during development
  • 📦 Optimized Production Builds - Minified, tree-shaken, and ES2020-compatible output
  • 🧪 Automated Testing - End-to-end testing with Playwright
  • 📏 Code Quality - ESLint, Prettier, and TypeScript integration
  • 🎯 Path Aliases - Clean imports with custom path mappings
  • 📋 Changesets - Automated versioning and changelog generation
  • 🌐 Webflow Ready - Optimized for Webflow custom code integration

🏁 Quick Start

Prerequisites

Ensure you have the following installed:

Installation

  1. Create a new repository from this template

    🔗 Use this template

    Note: You must be authenticated with a Fynd Design Engineering GitHub account

  2. Clone and install dependencies After creating a project with above template install all dependencies using pnpm

    pnpm install
  3. Start developing

    pnpm dev

    Open http://localhost:3000 to see your project in action!

🛠️ Development Workflow

Development Mode

Launch the development server with live reloading:

pnpm dev

What happens:

  • 📦 Bundles TypeScript files in real-time
  • 🌐 Serves files at http://localhost:3000
  • 🔄 Automatically reloads on file changes
  • 🗺️ Generates source maps for debugging
  • 📊 Displays a helpful table of served files with import suggestions

Production Build

Create an optimized build for deployment:

pnpm build

Build optimizations:

  • 🗜️ Code minification and compression
  • 🌳 Tree shaking to remove unused code
  • 🎯 ES2020 target for broad browser compatibility
  • 📁 Clean output in the dist/ directory

🧪 Testing & Quality Assurance

Running Tests

Execute end-to-end tests with Playwright:

# Run tests in headless mode
pnpm test

# Interactive test runner with UI
pnpm test:ui

Code Linting

Maintain code quality with ESLint:

# Check for issues
pnpm lint

# Auto-fix common problems
pnpm lint:fix

Code Formatting

Keep code consistent with Prettier:

pnpm format

Type Checking

Verify TypeScript types:

pnpm check

📦 Release Management

This project uses Changesets for professional version management.

Creating a Release

  1. Work on your feature branch (never commit directly to main)

    git checkout -b feature/your-feature-name
  2. Make your changes and build

    pnpm build
  3. Create a changeset

    pnpm changeset

    Follow the prompts to:

    • Select which packages changed
    • Choose the semantic version bump (patch/minor/major)
    • Write a clear summary of changes
  4. Commit your changes

    git add .
    git commit -m "feat: add your feature description"
  5. Publish the release

    pnpm release

Dependency Management

Keep dependencies up-to-date:

pnpm update

📁 Project Architecture

cdn-starter/
├── 📂 src/
│   ├── 📄 index.ts          # Main entry point
│   └── 📂 utils/            # Utility functions
│       └── 📄 *.ts          # Your utility modules
├── 📂 dist/                 # 🏗️ Build output (auto-generated)
├── 📂 tests/                # 🧪 Playwright test files
│   └── 📄 example.spec.ts   # Example test file
├── 📂 bin/                  # 🔧 Build tools
│   ├── 📄 build.js          # esbuild configuration
│   └── 📄 live-reload.js    # Development hot reload script
├── 📄 package.json          # Project configuration
├── 📄 tsconfig.json         # TypeScript settings
├── 📄 eslint.config.js      # ESLint rules
├── 📄 playwright.config.ts  # Test configuration
└── 📄 README.md            # This file

🛤️ Advanced Configuration

Multiple Entry Points

Build multiple files by updating bin/build.js:

const ENTRY_POINTS = [
  "src/home/index.ts", // → dist/home/index.js
  "src/contact/form.ts", // → dist/contact/form.js
  "src/shared/utils.ts", // → dist/shared/utils.js
];

Path Aliases

Use clean imports with pre-configured aliases:

// ❌ Avoid relative paths
import { helper } from "../../utils/helper";

// ✅ Use clean path aliases
import { helper } from "$utils/helper";

Available aliases:

  • $utils/*src/utils/*

Add more in tsconfig.json:

{
  "compilerOptions": {
    "paths": {
      "$utils/*": ["src/utils/*"],
      "$components/*": ["src/components/*"],
      "$types/*": ["src/types/*"]
    }
  }
}

🌐 Webflow Integration

Development Integration

For testing in Webflow during development:

  1. Start the dev server: pnpm dev
  2. Use the development URLs in Webflow:
    <script defer src="http://localhost:3000/index.js"></script>

Production Deployment

  1. Build your project

    pnpm build
  2. Upload to your CDN Upload files from the dist/ directory to your preferred CDN (Cloudflare, AWS CloudFront, etc.)

  3. Include in Webflow Run this to get the generated cdn links with the latest version available

    pnpm cdn

Best Practices for Webflow

  • Use defer for non-critical scripts
  • Minimize HTTP requests by bundling related functionality
  • Test thoroughly across different Webflow templates
  • Use semantic versioning for cache busting

🤝 Contributing

We welcome contributions! Please follow these guidelines:

  1. Fork the repository
  2. Create a feature branch
    git checkout -b feature/amazing-feature
  3. Make your changes following our code standards
  4. Run quality checks
    pnpm test && pnpm lint && pnpm check
  5. Add a changeset
    pnpm changeset
  6. Commit with conventional commits
    git commit -m "feat: add amazing feature"
  7. Push and create a Pull Request

Commit Convention

We follow Conventional Commits:

  • feat: New features
  • fix: Bug fixes
  • docs: Documentation changes
  • style: Code style changes
  • refactor: Code refactoring
  • test: Test additions or changes
  • chore: Maintenance tasks

📊 Performance Tips

  • Bundle analysis: Use esbuild's metafile option for bundle analysis
  • Code splitting: Consider splitting large applications into multiple entry points
  • Tree shaking: Write ES modules to enable automatic dead code elimination
  • Compression: Enable gzip/brotli compression on your CDN

🐛 Troubleshooting

Common Issues

Build failures:

# Clear node_modules and reinstall
rm -rf node_modules pnpm-lock.yaml
pnpm install

TypeScript errors:

# Check your tsconfig.json configuration
pnpm check

Live reload not working:

  • Ensure port 3000 is available
  • Check browser console for WebSocket connection errors
  • Verify firewall settings

📄 License

This project is licensed under the ISC License.