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

aws-lambda-chrome

v1.0.1

Published

A lambda compatible build of headless chrome.

Downloads

1

Readme

AWS Lambda compatible Chrome

This repository wraps a custom build of Chrome suitable for use on AWS lambda.

Usage

Requiring this module augments the LD_LIBRARY_PATH and PATH in order for chrome to find a custom build of NSS. This is necessary because the build of NSS on lambda is too old for newer versions of Chrome to boot with.

const { chromePath } = require('aws-lambda-chrome');
const { spawn } = require('child_process');

chromeProcess = spawn(chromePath, effectiveArgs, {
    env: process.env,
    /* TODO add required args here */
});

CLI Arguments

We have tested Chrome with following list of arguments:

--proxy-server=XXX
--remote-debugging-port=XXX
--user-data-dir=XXX
--disable-background-networking
--disable-breakpad
--disable-canvas-aa
--disable-client-side-phishing-detection
--disable-cloud-import
--disable-composited-antialiasing
--disable-default-apps
--disable-extensions-http-throttling
--disable-gpu
--disable-gpu-sandbox
--disable-kill-after-bad-ipc
--disable-namespace-sandbox
--disable-plugins
--disable-print-preview
--disable-renderer-backgrounding
--disable-seccomp-filter-sandbox
--disable-setuid-sandbox
--disable-smooth-scrolling
--disable-sync
--disable-translate
--disable-translate-new-ux
--disable-webgl
--disk-cache-dir=/tmp/cache-dir
--disk-cache-size=10000000
--ipc-connection-timeout=10000
--media-cache-size=10000000
--nacl-dangerous-no-sandbox-nonsfi
--no-default-browser-check
--no-experiments
--no-first-run
--no-pings
--no-sandbox
--no-zygote
--prerender-from-omnibox=disabled
--single-process
--window-size=1280,720

Note: these are provided only for reference. They are not guaranteed to work, and most of them are probably redundant.