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

megajs-me

v1.1.8

Published

Unofficial JavaScript SDK for MEGA

Downloads

44

Readme

MEGAJS

Unofficial JavaScript SDK for MEGA

Project status:
Development stalled. Issue and discussion requesting locked only to supporters. Looking for someone to lead this project as, me, qgustavor, I don't want to continue leading this project. As an example, I accepted this PR just because at least someone wanted to help! On the other hand it made the home page uglier! Why adding a npm install and import instructions in the home page?! Come on! It's already in the tutorial! Focus on the library main points in the home page instead! React does not have a npm install in the homepage, neither Vue, nor Angular. Svelte does but it's below the fold, after showing the main points of the library!

I don't care anymore! If someone wants to lead this project then make a fork, show that you really care about this project and I will let you to lead this project. You don't need to maintain the fork like me after tonistiigi, I will transfer the project to you.

API documentation and examples are available in the website: https://mega.js.org/

Contributing

pr-release JavaScript Style Guide

  • Fork the project
  • Clone it
  • Run npm install
  • Switch to a feature branch
  • Change the library as you want
  • Build the bundled versions using npm run build
  • Run at least Node tests using npm test node to test Node
  • Optionally run npm test deno to test Deno if you have it installed (CI will test Deno anyway)
  • Create a pull-request against next (not main)

Before creating a pull request, please, run tests. It will avoid a lot of common issues! You can run npm run lint-fix to fix common issues.

If you implement new features them implement tests for it too if possible. The hash at the end of test/helpers/test-runner.mjs may be updated if tests are updated in a way it change server state (like adding new files to tests).

Project history

This package started as a fork, with the following objectives:

  • Make the original package work in browsers again: even following the instructions from the original library it stopped working because some dependencies used __proto__, which is non-standard and isn't supported in many browsers. Also the updated versions of those libraries broke backyards compatibility;
  • Reduce dependencies and replace big dependencies with smaller ones, like crypto libraries, which usually are huge;
  • Rewrite code using the new JavaScript syntax, allowing to use Rollup, which can generate smaller bundles;
  • Make tests work again after the changes above;
  • Continue the original library development implementing new features and improving performance.

Request package was replaced with a shim based in browser-request and xhr-stream, which additional changes in order to make it work inside Service Workers. Crypto was replaced with secure-random.

As there were many changes there isn't any plan to merge those changes into the original library, unless the original author accept those massive changes. That's why I put "js" in the name, which is silly because both libraries use JavaScript. At least it's better than other ideas I had, like "mega2", "mega-es" and "modern-mega".

In 1.0 release request was replaced with fetch, Deno support was added (including tests), TypeScript types were added, Rollup was replaced with esbuild, streaming libraries were updated or replaced and some issues were fixed.