Greg Jacobs fragginwagon

London, Ontario, Canada
Joined on 2026-01-26

@fraggin/document-browser-kit (0.1.6)

Published 2026-05-06 17:40:09 -04:00 by fragginwagon

Set up this registry in your project .npmrc file:

@fraggin:registry=

To install the package using npm, run the following command:

npm install @fraggin/document-browser-kit@0.1.6

or add it to the package.json file:

"@fraggin/document-browser-kit": "0.1.6"

For more information on the npm registry, see the documentation.

@fraggin/document-browser-kit

Shared document-browser primitives used by the Pokemon rules browser and Datasift.

Package purpose

This repository owns product-neutral document-browser code:

generic search and browser state helpers
reusable Vue document-browser components and composables
shared build-time indexing utilities
shared base styles that are not product-branded

Pokemon-specific and Datasift-specific branding, content grouping, and app orchestration stay in their consumer repositories.

Validate and publish

The package publish workflow lives in .gitea/workflows/publish.yaml.

Make the shared change here.
Run the package validation locally:
```
npm run validate:ci
```
Bump package.json to the next version.
Commit the change and push it.
Push a matching vX.Y.Z git tag. The publish workflow only runs on v* tags.
Wait for the validation job and publish job to finish successfully.
Wait for the new package version to appear in the Gitea npm registry. There can be a short propagation delay after the tag is pushed.

Publishing is version-tag driven. A commit on its own does not publish a package.

Consumer update flow

After a shared slice is published:

Update pokemon-rules-browser with an explicit install:

npm install @fraggin/document-browser-kit@<version>

Update ~/Developer/Source Code/boilerplates/datasift/ the same way.
Run both consumer builds before treating the shared slice as complete.

Prefer an explicit versioned install over a plain npm install when moving consumers to a new release. That refreshes package-lock.json cleanly and avoids leaving a stale file-based or older registry resolution in place.

Release contract for extracted slices

When a reusable slice is first built in a consumer repo such as Pokemon:

Verify the behavior in the consumer.
Extract the smallest generic slice into this package.
Publish this package with a version bump and matching v<version> tag.
Wait for registry availability.
Move each consumer to the published version.
Re-run consumer builds.

That sequence keeps this package as the source of truth and avoids consumers depending on unpublished shared changes.

Dependencies

ID	Version
jsdom	^26.1.0
jszip	^3.10.1
mammoth	^1.10.0
pdfjs-dist	^4.10.38

Peer Dependencies

ID	Version
vue	^3.5.13

Details

npm

2026-05-06 17:40:09 -04:00

latest

24 KiB

Assets (1)

document-browser-kit-0.1.6.tgz 24 KiB

Versions (6) View all

0.1.6

2026-05-06

0.1.5

2026-05-06

0.1.4

2026-05-05

0.1.3

2026-05-04

0.1.2