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

netlify-to-vercel

v1.1.0

Published

This is a tool that allows you to quickly migrate your `netlify.toml` file into a `vercel.json`. No need to copy over redirects by hand!

Downloads

15

Readme

Netlify to Vercel Configuration Migrator

This is a tool that allows you to quickly migrate your netlify.toml file into a vercel.json. No need to copy over redirects by hand!

Instructions

You can optionally enter two settings for netlify-to-vercel:

  • --netlify_path : The path to the netlify.toml file to read (default: ./netlify.toml)
  • --vercel_path : The path to the vercel.json file to write (default: ./vercel.json)
  • --netlify_token : The auth token for accessing your Netlify environment variables. Generation instructions can be found here
  • --vercel_token : The auth token for accessing your Vercel environment variables. Generation instructions can be found here

Run the following (with optional flags):

npx netlify-to-vercel

You will first choose if you want to migrate your environment variables, and then you will pick the Netlify project to pull from. Finally, you will select the Vercel project you would like to save the variables to.

? Would you like to migrate environment variables? yes
? Which Netlify Team do you want env vars from? test
? Which Netlify Project do you want env vars from? helpful-cranachan-3774bc - https://github.com/Speediing/simon-game
? Which Vercel Team is your project in? jasonwikerpro
? Which Vercel Project do you want to save the variables at? nextjs-boilerplate
▲ Variables Updated

You will now be asked if you would like to migrate your netlify.toml file

? Would you like to migrate your netlify.toml to a vercel.json? yes
netlify.toml data is read
▲ vercel.json data is saved. ▲

If you have a netlify.toml file that looks like:

[Settings]
ID = "Your_Site_ID"

[build]
  base    = "project/"
  publish = "project/build-output/"
  command = "echo 'default context'"
  ignore = "git diff --quiet HEAD^ HEAD sub_dir/"

[[redirects]]
  from = "/*"
  to = "/blog/:splat"

[[redirects]]
  from = "/old-path"
  to = "/new-path"
  status = 301
  query = {path = ":path"} 

[[redirects]]
  from = "/*"
  to = "/index.html"
  status = 200
[[redirects]]
  from = "/api/*"
  to = "https://us-central1-netlify-intercom.cloudfunctions.net/readHeaders/:splat"
  status = 200


[[headers]]
  for = "/*" 
  [headers.values]
    X-Frame-Options = "DENY"
    X-XSS-Protection = "1; mode=block"
    Content-Security-Policy = "frame-ancestors https://www.facebook.com"
    Basic-Auth = "someuser:somepassword anotheruser:anotherpassword"

Your resulting vercel.json will look like:

{
  "redirects": [
    { "source": "/(.*)", "destination": "/blog/:splat", "permanent": true },
    {
      "source": "/old-path",
      "destination": "/new-path",
      "has": [{ "type": "query", "key": "path" }],
      "permanent": true
    }
  ],
  "rewrites": [
    { "source": "/(.*)", "destination": "/index.html" },
    {
      "source": "/api/(.*)",
      "destination": "https://us-central1-netlify-intercom.cloudfunctions.net/readHeaders/:splat"
    }
  ],
  "headers": [
    {
      "source": "/(.*)",
      "headers": [
        { "key": "X-Frame-Options", "value": "DENY" },
        { "key": "X-XSS-Protection", "value": "1; mode=block" },
        {
          "key": "Content-Security-Policy",
          "value": "frame-ancestors https://www.facebook.com"
        },
        {
          "key": "Basic-Auth",
          "value": "someuser:somepassword anotheruser:anotherpassword"
        }
      ]
    }
  ],
  "outputDirectory": "project/build-output/",
  "ignoreCommand": "git diff --quiet HEAD^ HEAD sub_dir/",
  "buildCommand": "echo 'default context'"
}