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

@pageloop/external

v0.6.1

Published

`ExternalIntegrationAdapter` implementations for the [PageLoop](https://github.com/rw3iss/pageloop) server — pull (or accept pushes of) content from third-party note/doc sources into a project. One subpath per provider; none pulls a heavyweight SDK (they

Readme

@pageloop/external

ExternalIntegrationAdapter implementations for the PageLoop server — pull (or accept pushes of) content from third-party note/doc sources into a project. One subpath per provider; none pulls a heavyweight SDK (they talk HTTP / parse files).

Install

pnpm add @pageloop/external

Exports

| Subpath | Provider | Auth mode | |---|---|---| | . | re-exports every provider factory below | — | | /notion | createNotionAdapter(config) — Notion | oauth-pull | | /evernote | createEvernoteAdapter(config) — Evernote | oauth-pull (OAuth 1.0a) | | /obsidian | createObsidianAdapter() — Obsidian | plugin-push |

Each factory returns an ExternalIntegrationAdapter you register with the Application's integration registry.

Notion is the only provider with a working content-fetch path today; Evernote and Obsidian are Phase 2 skeletons (auth/fetch methods throw not yet implemented). The adapter shape and registration wiring are stable.

. — all providers

import { createNotionAdapter, createObsidianAdapter } from '@pageloop/external';

/notion — OAuth 2.0 pull

import { createNotionAdapter } from '@pageloop/external/notion';

const notion = createNotionAdapter({
  clientId: process.env.PAGELOOP_NOTION_CLIENT_ID!,
  clientSecret: process.env.PAGELOOP_NOTION_CLIENT_SECRET!,
  // redirectUri defaults to the Application's baseUrl + the OAuth callback path
});

/evernote — OAuth 1.0a pull

import { createEvernoteAdapter } from '@pageloop/external/evernote';

const evernote = createEvernoteAdapter({
  consumerKey: process.env.PAGELOOP_EVERNOTE_CONSUMER_KEY!,
  consumerSecret: process.env.PAGELOOP_EVERNOTE_CONSUMER_SECRET!,
  env: 'sandbox', // 'production' once Evernote promotes the key
});

/obsidian — plugin push

No server config — the first-party Obsidian Sync plugin POSTs note changes with a user-minted Personal Access Token:

import { createObsidianAdapter } from '@pageloop/external/obsidian';

const obsidian = createObsidianAdapter();