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

@hamza221/wxp

v0.1.0

Published

Framework-independent Windows XP Luna web components

Readme

wxp

Framework-independent Windows XP default blue Luna components and a searchable component showcase. Native HTML supplies ordinary controls; browser-native JavaScript modules register interactive xp-* custom elements. Components use light DOM, not shadow DOM, and need no React or other runtime framework.

The Windows 95-inspired portfolio inspired the desktop presentation, not the visual target. This project targets XP's rounded blue frames, warm dialog surfaces, gradients, and control states—not Win95 teal and gray. Pixel identity with a native Windows XP installation has not been verified. See research and fidelity requirements.

Install locally with npm

The npm package name is @hamza221/wxp. It is configured for public publication but has not been published yet. Until the first release, create an installable archive from this checkout:

npm install
npm pack

In a consumer project, install the generated archive (adjust its path/version if necessary):

npm install /absolute/path/to/checkout/hamza221-wxp-0.1.0.tgz

A local-directory install is also possible:

npm install /absolute/path/to/checkout

Registry warning: the unscoped name wxp belongs to an unrelated package. After the first release, install this library with npm install @hamza221/wxp; until then, use the local archive or directory above.

The package exports are:

| Export | Purpose | | --- | --- | | @hamza221/wxp | ESM entry point; importing it registers xp-* elements in the browser | | @hamza221/wxp/styles.css | Component styles and shared tokens |

With a CSS-aware bundler such as Vite, import both in your application's browser entry module:

import '@hamza221/wxp';
import '@hamza221/wxp/styles.css';

Wrap component markup in .xp:

<section class="xp" aria-label="Profile settings">
  <form>
    <label for="profile-name">Name</label>
    <input class="xp-input" id="profile-name" name="name" value="Guest">
    <button class="xp-button" type="reset">Reset</button>
  </form>
</section>

The reset button above uses native form behavior; it does not require a custom event handler. Ordinary styled controls need only CSS. Interactive custom elements additionally require the ESM import. The component showcase supplies complete markup and each element's attributes, keyboard behavior, and bubbling custom-event details. Keep IDs unique when copying multiple examples.

For a browser-only deployment without a bundler, copy the package's complete src/ directory to a served asset directory, then link styles.css and load index.js with <script type="module"> from that directory. Preserve relative module/CSS paths. Browsers do not resolve bare npm specifiers or JavaScript CSS imports by themselves. Import/register elements on the client, not while rendering on a server.

Publish to npm

Publish from a clean checkout as the hamza221 npm account (or an authorized package maintainer). The package is public, uses GPL-3.0-or-later, and includes its complete browser source and license notices.

npm login
npm whoami
npm ci
npm run build
npm publish --dry-run
# Creates the public release; run only when ready:
npm publish --access public

Complete npm's browser/2FA authorization when requested; never commit tokens. After publishing, confirm with npm view @hamza221/wxp version and update the website's unpublished notices. Subsequent releases require a new version because npm versions cannot be overwritten. GitHub Pages deployment does not publish to npm.

Component scope

The library covers reusable control families rather than an operating-system emulator: buttons and form controls; grouping, progress, sliders and scrolling; navigation and data views; windows and dialogs; menus, toolbars, status bars and shell-style surfaces. The showcase is the API inventory for individual components. It is not a promise to reproduce arbitrary application-specific controls, every Win32 message, Explorer's filesystem, or Windows system services.

Use semantic HTML and explicit labels. Native disabled and form semantics remain important; visual resemblance alone is not accessibility. Custom composite widgets need their documented keyboard controls. Browser/OS-owned select popups, date pickers, scrollbars, font rasterization, and forced-color rendering can differ from XP.

Run the showcase

npm install
npm run dev

For a production site build, use npm run build; npm run preview serves that build locally. Vite is a development dependency, not a consumer runtime dependency.

The demo is hosted at hamza221.github.io/wxp. Pushes to main build and deploy it through .github/workflows/pages.yml. The Vite configuration uses /wxp/ as the asset base in GitHub Actions while local development stays at /.

The documentation is presented inside an Internet Explorer 6-inspired Windows XP frame: blue Luna caption, compact menu and toolbar bands, address field, Favorites pane, and bottom status bar. The page itself uses an early-2000s documentation layout with linked component indexes, compact headings, and live examples. Favorites and page content scroll independently; on narrow screens Favorites becomes a dismissible drawer. This is a modern-browser presentation, not an IE6 emulator or a pixel-identical reproduction.

The band arrangement is informed by Microsoft's Internet Explorer toolbar reference. Browser decoration and folder shapes use CSS and original drawings, not bundled Microsoft artwork. The same 43 component demos, source-copy controls, installation guide, and license texts remain available.

Verification

The production build and local npm archive installation were exercised in Chromium, including both public exports, a packaged modal, and form submission/reset. All 43 component documentation routes loaded. Browser smoke checks covered calendar and menu keyboard navigation, tab selection, numeric sorting, splitter/header bounds, window states, dialog focus restoration, wizard validation, taskbar restoration, rich-text formatting, property rollback, reset cancellation, mobile navigation, source copying/fallback, and license downloads.

This is not a full browser or assistive-technology compatibility audit. Native Windows XP screenshot equivalence remains unverified; see the research document for the required comparison conditions.

License and asset rights

New project code is licensed GPL-3.0-or-later. See LICENSE for the GPL text and COPYING for the project notice. XP.css-derived portions retain their MIT notice in THIRD_PARTY_NOTICES.

GPL is not the same licensing model as a permissively licensed component kit: when conveying covered software, recipients must receive the required notices, license, and corresponding source under the applicable GPL terms. Serving covered JavaScript to visitors delivers copies to their browsers; using a website does not make client-delivered code private server-only software. Bundling/minifying does not remove source obligations. Whether surrounding application code forms a combined covered work depends on the integration; review that before incorporating this library into a proprietary application. Merely running private modified software is different from conveying it. This summary is not legal advice; the license controls.

No original Microsoft Windows icons, fonts, or wallpaper are bundled. Tahoma and Trebuchet MS are requested only from fonts already installed on the user's system, with fallbacks. Public availability of Windows assets in another repository is not a verified redistribution license. This is an independent recreation, not a Microsoft product or endorsement.