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

jscad-mylib

v0.0.5

Published

This template provides a minimal setup to publish a JSCAD package and uses React to render a simple user interface to test the output of the JSCAD package.

Downloads

11

Readme

React + TypeScript + Vite + JSCAD

This template provides a minimal setup to publish a JSCAD package and uses React to render a simple user interface to test the output of the JSCAD package.

Getting started

Create a new github repository from this template (more info here) and clone the repository to your local machine.

Install dependencies

npm install

Start the development server with npm run dev, you should see a cube in the preview window.

Edit lib/main.ts and src/App.tsx file to create your JSCAD package and adapt the dev preview UI to get a preview of your JSCAD package output.

Building your package

To build your package run npm run build. This will create a dist folder with the compiled package. Check the files in the dist folder to make sure everything is correct.

Publishing your package

First be sure to update the name and version fields in package.json before publishing. It is also a good idea to modify this README.md explaining what your package does and how to use it.

To publish your package to npm run npm publish. This will publish your package to npm and make it available for others to use.

If you want to publish the package to the public you have to set private: false in package.json to allow publishing. The first time you publish a public package you also need to append --access public to the publish command.

npm publish --access public

Using your package on jscad.app

If you have published your package you can use it on the jscad.app website like so:

const { randomCube } = require("jscad-mylib");

function main() {
  randomCube({ minSize: 1, maxSize: 10 });
}

module.exports = { main };

Note: If you update your plugin and jscad.app does not pick up the new version, it may be necessary to request purging the jsDelivr cache. You can do this here: jsdelivr.com/tools/purge

Expanding the ESLint configuration

If you are developing a production application, we recommend updating the configuration to enable type aware lint rules:

  • Configure the top-level parserOptions property like this:
export default {
  // other rules...
  parserOptions: {
    ecmaVersion: "latest",
    sourceType: "module",
    project: ["./tsconfig.json", "./tsconfig.node.json"],
    tsconfigRootDir: __dirname,
  },
};
  • Replace plugin:@typescript-eslint/recommended to plugin:@typescript-eslint/recommended-type-checked or plugin:@typescript-eslint/strict-type-checked
  • Optionally add plugin:@typescript-eslint/stylistic-type-checked
  • Install eslint-plugin-react and add plugin:react/recommended & plugin:react/jsx-runtime to the extends list