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

@cedraz/teste-vite-tailwind

v0.0.1

Published

This package is the open source UI that is used for the courses on [hungrimind.com](https://hungrimind.com).

Downloads

2

Readme

Course Kit

This package is the open source UI that is used for the courses on hungrimind.com.

Course User Interface

It takes in a JSON file as an input, and handles everything courses related within the component. Inside the GitHub repo in the test folder you can find a test.json file.

The JSON file is a course id followed by a list of lessons. There are 3 lesson types, and each lesson type has specific fields. Below are the possible lesson types and fields

| Lesson Type (defined by sectionType in JSON) | Field Name | Field Description | | ---------------------------------------------- | -------------- | ------------------------------------------------------------------------------------------------------------------------------ | | "header" | sectionType | Has to be "header". | | | id | Identifier for that lesson. | | | image | Main promo image for the course. | | | links | List of links to showcase. Need to contain type and url fields. Currently only "github" and "discord" types are available. | | | content | Markdown section describing the course or persuading them to take it. Or it can contain whatever markdown you desire. | | | headline | Name of the course. | | | subheadline | Subtitle of the course. | | "slide" | sectionType | Has to be "slide". | | | id | Identifier for that lesson. | | | type | Can contain either image or code. Currently "image", "flutter", "yaml", "md" are supported. | | | content | Markdown explaining the section topic. | | | value | Depending on the type can be either a link to image or code. | | | heading | Title for the slide. Used for table of contents as well. | | | file | Name of the file for code snippets. optional, and only for code types | | | highlight | Which lines should be highlighted in the code snippets. optional, and only for code types | | | previewImage | A preview image of what UI should look like for the code. optional, and only for code types | | "md" | sectionType | Has to be "md". | | | id | Identifier for that lesson. | | | content | Markdown. | | | heading | Title. Used for table of contents as well. |

Local development

First run

  1. Clone this repository
  2. run make link
  3. run make install
  4. run make watch
  5. run either make astro or make next depending on which framework you want to use.

Subsequent runs

Run step 4 and 5 from the above list.