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

extendscript-ponyfills

v1.1.1

Published

Modern JavaScript ponyfills for ES6. Intended for use with Extendscript.

Downloads

137

Readme

extendscript-ponyfills

Why

ExtendScript is stuck in ES3, but we like our simple ES6 methods. A common solution is to polyfill these methods, but I'll let sindresorhus and hyperbrew explain why that's not a good idea, especially so in Adobe-land.

Usage

npm i extendscript-ponyfills
import { arrayFrom, forEach } from "extendscript-ponyfills";

(function script() {
	const comp = app.project.activeItem;

	if (!(comp && comp instanceof CompItem)) {
		return alert("No comp found.");
	}

	const layers: Layer[] = arrayFrom(comp.layers);

	if (layers.length) {
		forEach(layers, (layer) => alert(layer.name));
	} else {
		alert("No layers found.");
	}
})();

Or, download the latest release to #include in your .jsx script.

// @include "path/to/extendscript-ponyfills-vX.X.X.jsx"

(function script() {
	var comp = app.project.activeItem;

	if (!(comp && comp instanceof CompItem)) {
		return alert("No comp found.");
	}

	var layers = PONIES.arrayFrom(comp.layers);

	if (layers.length) {
		PONIES.forEach(layers, function (layer) {
			alert(layer.name);
		});
	} else {
		alert("No layers found.");
	}
})();

By default the ponyfills are namespaced to PONIES—you can change this name on the first line of the .jsx, or remove the IIFE entirely.

Ponyfills

Array

  • arrayFrom
  • difference
  • differenceWith
  • every
  • fill
  • filter
  • find
  • findIndex
  • flat
  • flatMap
  • forEach
  • groupBy
  • includes
  • indexOf
  • intersection
  • intersectionWith
  • isArray
  • lastIndexOf
  • map
  • reduce
  • some

String

  • padEnd
  • endsWith
  • includes
  • padStart
  • repeat
  • startsWith
  • trim

Object

  • assign
  • entries

Function

  • bind

Similar Projects