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

@mariamaneva/js-playground

v0.9.16

Published

A simple framework for testing js code snippets

Downloads

5

Readme

Description

JS Playground

This is a simple JS/TS code playground framework that I created in order to test code snippets, play Advent of Code, etc a while ago. As my original project got larger, I decided to encapsulate the code-running logic in a package.

All the playground files are listed in a clickable sidebar explorer. Nesting is possible too. To test the output you can use both the DOM and Devtools console.

You can see the updated output after each save as well.

Usage

  1. Install the package
npm install @mariamaneva/js-playground
  1. In your root package.json file, add the following script commands:
"scripts": {
  // add these lines
  "start": "npm run start --prefix node_modules/@mariamaneva/js-playground",
  "new-page": "npm run new-page --prefix node_modules/@mariamaneva/js-playground",
  "update-nav": "npm run update-nav --prefix node_modules/@mariamaneva/js-playground",
  "help": "npm run help --prefix node_modules/@mariamaneva/js-playground"
}
  1. Create a new playground page:
npm run new-page --path <your_page_name>.js

OR

npm run new-page --path <your_page_name>.ts
  1. Start the project
npm start
  1. Open <your_page_name>.js file from the sections folder and add your code where the // code comment is. As you keep updating and saving you can monitor your output in the respective page within the browser.

Adding a new page

Repeat step 3 and re-run the project every time you need a new playground file.

Updating the sidebar explorer

If you deleted any files from the sections folder, run npm run update-nav and re-start the project to update the sidebar explorer