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

@atlaskit/collab-provider

v10.2.0

Published

A provider for collaborative editing.

Downloads

2,921

Readme

Integrating with Collab-Provider

This guide outlines two primary use cases for integrating with the collab-provider.

Use Cases

  1. Full Integration: FE Events and BE API Calls
    • For scenarios requiring both front-end events and back-end API interactions, the back-end APIs are hosted by pf-collab-service. To determine if API calls are necessary, please refer to the OpenAPI documentation, specifically under the Service to Service section.
  2. Partial Integration: FE Events Only
    • For scenarios where only front-end events are needed, without back-end API interactions.

Integration Details

  1. Full Integration: FE Events and BE API Calls
    • Ensure the provider is initialized with:
      • DocumentService from document-service.ts
      • Api from api.ts
  2. Partial Integration: FE Events Only
    • Ensure the provider is initialized with:
      • NullDocumentService from null-document-service.ts
      • NullApi from null-api.ts

For a detailed comparison of these integration approaches, refer to the source code in ../platform/packages/editor/collab-provider/src/provider/index.ts

// Full integration
- setup({getState, onSyncUpError}: {getState: () => EditorState; onSyncUpError?: SyncUpErrorFunction;})

// Partial Integration, initialize the provider with passing config isPresenceOnly as true
- setupForPresenceOnly(clientId: string)

Support

If you have further questions or require assistance, please reach out to the #team-cc-editor-services on Slack.