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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@baalspots/now

v2.2.0

Published

A custom Frontity builder for deploying to Vercel

Downloads

12

Readme

Frontity Vercel Builder

Deploy your Frontity project to Vercel.

Before deploying

  1. Include the following settings in your projects vercel.json file:
{
  "builds": [
    {
      "src": "package.json",
      "use": "@baalspots/now"
    }
  ],
  "buildCommand": "node -v && npx frontity build && node -v",
  "devCommand": "npx frontity dev",
  "framework": null,
  "installCommand": "npm i",
  "outputDirectory": "build"
}
  1. Update your Frontity projects local dev environment to use Node 16.

  2. Update package.json at the root of your project to use the following Node engine and scripts:

"engines": {
 "node": "16.x"
},
"scripts": {
 "dev": "npx frontity dev",
 "build": "node -v && npx frontity build && node -v",
 "serve": "npx frontity serve"
},
  1. Remove all package-lock.json files and node-modules folders in your Frontity project.

  2. Remove package-lock.json from your projects .gitignore file

  3. Run npm i at the root of your project.

Hotfix for @loadable/component default export error

This is a temporary fix for the @loadable/component bug reported on Dec 19. Once this issue is resolved by the maintainers at @loadable/component, the following code snippets should be removed.

  1. Add the following dependency to your projects root package.json file:
"@loadable/component": "5.15.3",
  1. Add the following override settings to the end of your projects root package.json file:
"overrides": {
  "@loadable/component": "5.15.3"
}
  1. Remove all package-lock.json files and node-modules folders in your Frontity project.
  2. Run npm i at the root of your project.

Example package.json file

{
  "name": "frontity-project",
  "description": "Frontity project",
  "engines": {
    "node": "16.x"
  },
  "scripts": {
    "dev": "npx frontity dev",
    "build": "node -v && npx frontity build && node -v",
    "serve": "npx frontity serve"
  },
  "dependencies": {
    "@loadable/component": "5.15.3",
    ...
  },
  "devDependencies": {
    ...
  },
  "overrides": {
    "@loadable/component": "5.15.3"
  }
}