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

clark-schedule

v1.0.0-rc.0

Published

Clark schedule

Downloads

1

Readme

Clark Schedule

NPM

Getting Started

  • You will need to install Yarn for dependency management, if you do not have it already installed.

  • Run the yarn command to install node_modules

Testing library integration locally

To test clark-styles locally, run yarn build. Make sure build/ directory exists and then follow the instructions here.

Testing

We use jest for running our test suite. All new utility functions should be pure and thoroughly unit-tested. Run yarn test to start the test runner

Flow

This project uses flow to do static typechecking. We're using the flowtype eslint plugin to enforce adding flow annotations to all files and stylistic consistency.

Run yarn flow to start the flow server. If you run into unexpected failures, as a first troubleshooting step, run yarn flow stop and then start the server again to bust the cache.

Updating

For convience sake, we use the cut-release project to easily publish to npm and follow SEMVER. Don't forget to update the changelog!

Once you have cut a release remember to bump the version in your project.

Usage

To use the library run yarn add clark-schedule.

import React from 'react'
import Schedule from 'clark-schedule';

const App = () => (
  <Schedule
    onSelectEvent={event => dispatchPush(`sessions/${event.id}`)}
    onSelectSlot={({ start, end }) =>
      dispatchPush({
        pathname: `tutors/${tutor.id}/sessions/new`,
        state: { start, end },
      })
    }
    events={transformTutorSessionsToCalendarEvents(tutorSessions, clients)}
  />
);

License

MIT © hiclark