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

@niiwin/core

v3.0.9

Published

This repo contains the source code for the Niiwin Rails engine and npm package. Find out more about Niiwin at https://niiwin.ca

Downloads

47

Readme

Niiwin

This repo contains the source code for the Niiwin Rails engine and npm package. Find out more about Niiwin at https://niiwin.ca

Getting started for Niiwin Core Developers

Follow these steps if you are a Niiwin Core Developer and you work on the Niiwin RubyGem, npm package, or dev toolchain:

Prerequisites

You'll need the following installed to continue setting up your development environment:

  • A Ruby version manager/switcher (rbenv, rvm, chruby, asdf, etc.)
  • Node.js (14.21.3+)
  • Yarn (1.22.0+)
  • Postgresql (9.6+)
  • Redis (6+)
  • Optional: The 1Password CLI1

Install Ruby

This assumes you have rbenv installed, though another Ruby version manager will also work.

  • Check that the required Ruby version 3.2.2 is installed: rbenv versions
  • Install it if it's not installed yet: rbenv install 3.2.2
  • Set global Ruby version to 3.2.2: rbenv global 3.2.2

Install the Niiwin gem and related repos

Since you are developing the Niiwin gem alongside an application, you will clone the Niiwin code repo and use a locally sourced version of the gem.

The niiwin-test app is configured to use your local Niiwin Engine gem source, and not the one hosted online. This is so that you can test your work in progress. In order for this to work, you need your code repos set up in the following way:

<niiwin-parent-folder>              # A container for the niiwin related repos
├── niiwin                          # The Niiwin Engine gem (this repo)
├── niiwin-technical-documentation  # Niiwin technical documentation
└── niiwin-test                     # THe Niiwin Engine test suite

The niiwin-technical-documentation repo is not required to run tests, however, it uses the niiwin-test repo to generate some automated diagrams, so it needs to fit into this folder structure as well.

  • cd into the <niiwin-parent-folder>
  • Clone the repo git clone [email protected]:animikii/niiwin.git

Optional tip: You can define a shell environment variable to store the path to the niiwin engine gem in your shell profile (ex: ~/.zshrc or ~/.bashrc).

# Set up path to niiwin engine gem source
export NIIWIN_GEM_SOURCE="/Users/momo/Code/niiwin"

Install dependencies

Make sure you are in the Niiwin gem root directory, then:

bundle install
yarn install
yarn build

Generate a new Niiwin App

You will use a locally sourced version of the niiwin-init script. In order to do so you will specify a custom path to the Niiwin gem source (/path/to/local/niiwin). Note that you can use this approach also to test the niiwin-init script itself:

/path/to/local/<niiwin-parent-folder>/niiwin/bin/niiwin-init --name my-awesome-app --path /path/to/local/<niiwin-parent-folder>/niiwin

# OR if you set up the NIIWIN_GEM_PATH environment variable above
$NIIWIN_GEM_SOURCE/bin/niiwin-init --name coworking --path $NIIWIN_GEM_SOURCE

Once the script is done, cd into the new app's root directory and start the app:

.bin/dev

In a browser, visit http://localhost:3000, and use the "Dev Login" button at the bottom of the page to choose a role and log in.

Now you can start working on the new Niiwin App, or on the Niiwin Engine itself.

NOTE: when providing a custom path to the niiwin gem to the niiwin-init script, that absolute path will be inserted into the app's Gemfile for the niiwin entry. If you plan on sharing the app's code with other developers, you should change the absolute path to the niiwin gem to a relative one: Change gem "niiwin", path: "/absolute/path/to/niiwin" to gem "niiwin", path: "../niiwin".