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

@mpv-easy/mpsm-scripts

v0.1.9-alpha.1

Published

@mpv-easy/mpsm-scripts

Downloads

5

Readme

@mpv-easy/mpsm-scripts

This repository is responsible for maintaining commonly used js scripts and making them installable via @mpv-easy/mpsm. Each script can be used individually or in combination, and will try to avoid functional conflicts caused by multiple scripts.

meta info

In order to be recognized by mpsm, you need to add some information at the beginning of the script

We use the idea similar to the tampermonkey script.

js

// ==UserScript==
// @name         autoload
// @version      0.1.1
// @description  Automatically load playable files
// @author       mpv-easy
// @downloadURL  https://github.com/mpv-easy/mpsm-scripts/releases/latest/download/autoload.js
// ==/UserScript==

lua

-- ==UserScript==
-- @name         autoload
-- @version      0.1.1
-- @description  Automatically load playable files
-- @author       mpv-easy
-- @downloadURL  https://github.com/mpv-easy/mpsm-scripts/releases/latest/download/autoload.js
-- ==/UserScript==

add a new script

scripts.json

If your script already has meta info, you can add it directly to the scripts.json

"speed": "https://github.com/mpv-easy/mpsm-scripts/releases/latest/download/speed.js",

meta.(js|lua)

If there is no meta info in the script, you can create a meta info file in meta and then add the meta info file to scripts.json

"open-file-dialog": "https://github.com/mpv-easy/mpsm-scripts/releases/latest/download/open-file-dialog.meta.lua",

script name

The script file name should be consistent with the script name in meta, in order to avoid problems in some extreme cases. If you encounter problems, please open an issue

dev

fish

set -x MPV_SCRIPT_DIR=/your_mpv_dir/portable_config/scripts ; pnpm run dev

bash

export MPV_SCRIPT_DIR=/your_mpv_dir/portable_config/scripts && pnpm run dev