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/create-sdk

v1.7.2

Published

This package is necessary in order to run `npm create @netlify/sdk`. When running `npm create @netlify/sdk`, npm will automatically search for a package called `@netlify/create-sdk` in order to run the initialization

Downloads

286

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

youvalvyouvalvberdavberdavvitaliyrvitaliyrsmnhsmnhdenar90denar90kathmbeckkathmbeckrj-netlifyrj-netlifyakardetakardetpiehpiehhrishikeshkhrishikeshksarahettersarahetterorinokaiorinokaiericapericapseanrobertsseanrobertsskn0ttskn0ttmikewenmikewenbiilmannbiilmannmarcus.netlifymarcus.netlifyjgantunesjgantuneseduardoboucaseduardoboucasnetlify-botnetlify-botnasibanasibaascorbicascorbic

Keywords

Readme

create-sdk

This package is necessary in order to run npm create @netlify/sdk. When running npm create @netlify/sdk, npm will automatically search for a package called @netlify/create-sdk in order to run the initialization

More info: https://docs.npmjs.com/cli/v9/commands/npm-init#description

How to try out a local version when contributing

If you're changing code in this repository, you can follow these steps to test out your changes:

  1. Build the project using pnpm build
  2. Run chmod +x ./dist/index.js
  3. Then run ./dist/index.js relative to the directory that you want to test it in.

If you also want to test out the local version of the SDK, you can provide a path to the SDK's bin directory using the LOCAL_SDK_BIN_PATH environment variable. This path needs to be relative to the directory that the create-sdk package creates.

  • npm: LOCAL_SDK_BIN_PATH=./path/to/the/sdk ./dist/index.js
  • pnpm: LOCAL_SDK_BIN_PATH=./path/to/the/sdk/bin/index.js ./dist/index.js

This logic does not work well with yarn right now so it is not recommended trying to use yarn to test out local changes.