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

@flycode-org/netlify-plugin-flycode

v0.0.5

Published

Netlify Build plugin - Inject FlyCode SDK to start editing your app

Downloads

4

Readme

Netlify Build plugin — FlyCode

Usage

Installation

In order to use this plugin, install it as a dependency to your project using

npm install --save @flycode/netlify-plugin or yarn add @flycode/netlify-plugin

Configuration

Next (and last) step is to use this plugin in Netlify config file.

If you don't have such file, create netlify.toml file in your project's root directory with contents:

[[plugins]]
package = "@flycode-org/netlify-plugin-flycode"

If netlify.toml already exists in your project, add the code above at the end of that file, to achieve similar result:

[[plugins]]
package = "..."

[[plugins]]
package = "..."

[[plugins]]
package = "@flycode-org/netlify-plugin-flycode"

And that's it! 🎉

Make sure to commit changes made to this file and either merge these to the main branch through a Pull Request or push directly.

In your next Netlify deploy you should see the plugin in action.

Advanced options

Instead of configuring the plugin to be used in every deploy, you can configure it to be executed only in certain cases.

The case we focus on is Deploy Preview, so if you want to avoid running this plugin on production deploy (see below why it's not a big deal), you might want to add this to the netlify.toml instead:

[[context.deploy-preview.plugins]]
package = "@flycode-org/netlify-plugin-flycode"

Why [[plugins]] is no big deal

Our plugin will proceed with its job only if it detects the current context is Deploy Preview. This means that when it's a Production deploy, you will most likely see a message:

Not a deploy preview. Skipping...

And that will conclude our plugin's life.

Debugging

Debugging allows you to view during its execution a stringified data that is used in the plugin. This includes:

  • netlifyConfig
  • process.env variables
  • inputs
  • constants
  • git metadata
  • and html that is injected

For debugging options, you can specify a debug mode as shown below:

[[plugins]]
package = "@flycode-org/netlify-plugin-flycode"

  [plugins.inputs]
  debug = true

For the deploy-preview context:

[[context.deploy-preview.plugins]]
package = "@flycode-org/netlify-plugin-flycode"

  [context.deploy-preview.plugins.inputs]
  debug = true