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

fcrypto

v0.1.0

Published

Another attempt implement fast cryptography for JavaScript

Downloads

2

Vulnerabilities

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

Links

Git

Maintainers

fanatidfanatid

Keywords

secp256k1

Readme

fcrypto

3 years ago I started work on Node.js bindings to bitcoin-core/secp256k1. Right now I'm not sure why exactly I start work on this, I think because there was no fast secp256k1 implementation for Node.js required for cryptocurrencies. There was few months of hard work. As result cryptocoinjs/secp256k1-node received Node.js bindings (with NAN), pure js based on elliptic & bn.js (which got performance and fixing patches) and new pure js implementation (mostly it was for educational purposes, but in this way elliptic and bn.js was improved).

Time is going and with every new Node.js version it's harder support bindings with NAN. Compilation issues still exists and developers create issues about new features. In same time, N-API became very stable (It's surprised, but from January 2020 N-API will be available as non-experimental feature in any maintained Node.js version), WebAssembly can be used in 88.66% of browsers and ecosystem grow fast.

So, I started new project and call it fcrypto.

fcrypto means fast crypto. Plan is provide Node.js bindings based on N-API and WebAssembly for browsers (or for Node.js if addon can not be built).

Currently supported:

Installation

fcrypto releases includes prebuilt addons for Linux (x64), MacOS and Windows (x64). But everything for building addon from distributed package included too, so you able check code and compile own addon.

By default ignore-scripts in yarn and npm set to false, so on installation package manager will try build addon and you will use own builded version, but if building fails, do not worry. If you have OS in list which listed above, precompiled addon will be used, if not, then WebAssembly will be used.

It's highly recommended set ignore-scripts to true. See info on npm or you can search in google about it.

yarn config set ignore-scripts true
npm config set ignore-scripts true

Loading process

If you use fcrypo directly or indirectly through dependencies, it's required wait loading first. Libraries should not be responsible for this. For example, in project entrypoint:

require('fcrypto').load().then(startApp)

LICENSE

This library is free and open-source software released under the MIT license.