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

@ikenga/pkg-wikipedia

v0.1.1

Published

Wikipedia webview package — the native child-webview proof for Phase 1

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

nedjameznedjamez

Keywords

Readme

@ikenga/pkg-wikipedia

Wikipedia in a native Ikenga child webview.

Why this package exists

It is the native-path proof for Phase 1. The other three proof-of-concept packages (Spotify for Artists, Sentry, Notion) all run in Managed Chrome (engines: ["chrome"]) because Google blocks OAuth from embedded browser user agents, so none of them can complete login inside a WebKit surface — see the plan's 02-research-external.md §"Embedded OAuth SSO Limits & ToS Restrictions".

That research is correct, but it left Phase 1 unable to prove itself: a Managed-Chrome package opens its own OS window, so it exercises no in-shell pane, gives the pane-chrome session control nothing to attach to, and creates no webjars/<pkg>/<partition>/ jar to wipe.

Wikipedia needs no login at all and permits embedding, so it exercises the whole native path end to end:

  • ui.routes[].kind: "webview" + capabilities.webview.child_webviews → mounts as an in-shell child webview on the default webkit engine
  • a route-level partition → a real jar at webjars/wikipedia/persist:wikipedia/
  • ui.session.persistence: "clear-on-exit" → exercises the wipe path, which the three keep packages never would
  • allowed_origins with both an apex and a subdomain glob → exercises both matcher shapes

Verify

ikenga dev ikenga-pkgs/packages/apps/wikipedia

Expected: the page renders in a pane (not a separate OS window), the pane chrome shows a session indicator reading "clear on exit", and webjars/wikipedia/persist:wikipedia/ exists on disk after first load and is gone after the app quits.