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

k8s-bitbucket-pipeline

v0.3.52

Published

Auto deployment in Cloudflare workers for static code (react, angular, vanilla, html & css, ...)

Downloads

1,882

Readme

README

Auto deployment in Cloudflare workers for static code (react, angular, vanilla, html & css, ...)

How do I get set up?

bitbucket-pipelines.yml

We can't push a .env in the repo so, we need to add the environment variables

            - export NODE_ENV=dev
            - export REACT_APP_API_DOMAIN=$STAGING_REACT_APP_API_DOMAIN
            - export REACT_APP_API_DOMAIN_V1=$STAGING_REACT_APP_API_DOMAIN_V1

Add the following lines to the bitbucket-pipelines.yml step you want to configure

            - npm i cloudflare-static-deployment
            - npx deploy -e staging 
  • Configuration
  • Dependencies
  • Database configuration
  • How to run tests
  • Deployment instructions https://docs.google.com/spreadsheets/d/1ND0mAcpdiukd9Fc9LLPVUqPjM3LCicschcFlGQsSzQw/edit#gid=0

Contribution guidelines

  • Writing tests
  • Code review
  • Other guidelines

Who do I talk to?

  • Repo owner or admin
  • Other community or team contact

external-ports or external-ips

add this in Workspace variables for bitbucket this way:

K8S_NODE_${i}=${port}

i.e.

K8S_NODE_1 = 1.1.1.1 K8S_NODE_2 = 1.1.1.2