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

@desmodder/graph-state

v0.2.3

Published

Typescript definitions for all possible Desmos graph states.

Downloads

10

Readme

Graph State

Typescript definitions for all possible Desmos graph states.

Quote from the API docs:

Warning: Calculator states should be treated as opaque values. Manipulating states directly may produce a result that cannot be loaded by GraphingCalculator.setState.

This repository is for people who want to throw caution to the wind and spurn that advice to make their own projects manipulating the graph state. The definitions themselves are in state.ts; everything else is testing code.

This is an unofficial project and may neither be perfectly complete nor accurate. However, I have made a best effort at testing it on many graphs.

Desmos is subject to change at any time, and this repository may become out-of-date or otherwise incorrect, so use it with caution.

Specifics

Any graph state obtainable through Calc.getState() should be accepted by the State interface. (If you have any incompatabilities, raise them on the GitHub issue tracker).

There are some properties where the State interface is broader. For example, default properties (such as hidden: false on an expression) are never included in the graph state from Calc.getState(), but they are allowed in the type definitions because scripts may want to output a state that includes the properties without needing to handle excluding the property (such as by using hidden: booleanVariable), and Desmos handles these as expected.

Keep in mind that the Desmos server does not perform full server-side validation on uploaded graph states, so a user could set them to anything by changing the server request. Similarly, Calc.setState() expands the full set of possible graph states; for example, it accepts numbers in place of Latex.