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

win-rader

v1.0.95

Published

Windows 95 running inside Grader.JS. No affiliation with Microsoft.

Downloads

60

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

dosydosy

Keywords

devtoolstaurideskgapnw.jscarloproton nativereactxpquasargraffitielectrinonodeguiqtflutterchromelyelectron.netqt5nodehybriddesktoptemplateelectronscitergradebrcross-platform appschromiumchromegrader-basegrader

Readme

winrader

Windows 95 in Grader.JS. Yep, it's the whole thing. I'm not sorry.

license

Copyright (c) 2020, Dosyago and/or its affiliates. All rights reserved.

This is a release of winrader, demonstrating Windows 95 in a cross-platform executable built using Grader, an cross-platform app builder.

License information can be found in the LICENSE file.

Nothing in the license makes any claim over any part or whole of the Windows 95 images used in releases.

This source-code, excluding any Windows 95 images, is dual-licensed. For information about commercial licensing, see Dosyago Commercial License for OEMs, ISVs and VARs.

This project is provided for educational purposes only. I do not own any of the Windows related trademarks used herein, and this project is not affiliated with and has not been approved by Microsoft, and has no official connection to or endorsement from Microsoft, or any other trademark holder.

key stats

  • development time: < 2 hours
  • lines of code: < 100

to run this from source

  1. you need to glone the repo
  2. npm install
  3. you need a windows95.img file. I got mine from felixrieseberg's releases
  4. npm test

to build the binary

Assuming you've already done the above steps to run from source, then do:

$ ./scripts/compile.sh

nerd warning

WARNING: This project uses Google Chrome to display the UI. Running this will download and install Google Chrome if you don't already have it installed. If you are allergic to Google Chrome, please avoid running or ingesting this binary.

security warning

WARNING: Normally, for security, GraderJS will inflate the app contents from the virtual filesystem inside the binary every time you run yer app. But because this project is so massive (it uses a OS image), inflating takes a long time, so I add a "hack" in the launcher.js code to only inflate it the first time, to save you time for your convenience. This makes your on-disk code vulnerable to malicious editing. For example someone could overwrite your index.html file because we don't refresh it every time.

related projects