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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@picsart/react-photo-editor

v1.0.2

Published

React component for embedding the Picsart Photo & Video Editor (Create) SDK in web applications

Downloads

51

Readme

@picsart/react-photo-editor

React component that loads the official Picsart Create SDK from sdk.picsart.io (script tag) and mounts the editor into your page. No bundled copy of the editor runtime is shipped in this package—only a thin React wrapper.

Install

npm install @picsart/react-photo-editor

Peer dependencies: React 17+ and react-dom.

Usage

Callers must set the same core fields as the Picsart quick start: apiKey, customerId, propertyId. The component renders the editor container and passes a matching containerId to the SDK (you can set containerId yourself, or omit it to get a stable auto-generated id). title defaults to Photo Print Designer if omitted.

import { PicsartEditor } from '@picsart/react-photo-editor';

export function Page() {
  return (
    <PicsartEditor
      apiKey={process.env.NEXT_PUBLIC_PICSART_API_KEY!}
      customerId={process.env.NEXT_PUBLIC_PICSART_CUSTOMER_ID!}
      propertyId={process.env.NEXT_PUBLIC_PICSART_PROPERTY_ID!}
      containerId="my-editor-root"
      title="Photo Print Designer"
    />
  );
}

SDK script URL

By default the component loads https://sdk.picsart.io/cdn.min.js. If that URL does not match your SDK version, pass sdkScriptUrl (see Picsart docs for the correct cdn?... URL).

Ref (imperative API)

const ref = useRef<PicsartEditorRef>(null);
<PicsartEditor ref={ref} ... />
ref.current?.export();
ref.current?.getInstance();

Publish to npm (@picsart org)

npm whoami
npm login
npm run publish:npm
  • Your npm user must be a member of the @picsart organization with permission to publish scoped packages.
  • This repo’s .npmrc and publishConfig.registry target https://registry.npmjs.org/ (not GitLab).

If npm publish returns 404 on PUT …/@picsart%2freact-photo-editor, npm is almost always telling you the current login cannot publish that scope (or you are not logged in). Fix org membership / use npm login, then retry.

To ship a new version after changes, bump version in package.json, then run npm run publish:npm again.

Local example

npm run dev:example

Configure example/.env from example/.env.example.