@feugene/unplugin-granularity

Internal only: the resolver’s behaviour and its public surface are unchanged.

Added

• Drift gate: the whitelist is checked against what the core actually ships. The manifest is maintained by hand on purpose — that keeps the resolver deterministic and free of I/O — but nothing punished it for drifting. The package’s own tests compare the resolver’s output against the same literals that are baked into it, so they stay green when a directive is renamed in the core or a component subpath stops existing. Component packages get that from granular doctor; the resolver has no granular provider, so the doctor has nothing to inspect here.

  The gate reads the core’s package.json#exports, not its sources: what the resolver hands a consumer is an import string, and it lives exactly as long as that key is published. It checks both directions — every whitelisted directive points at a live subpath and really exports its named binding, and every ./directives/* the core publishes is known to the resolver (globalDirectives excepted as an aggregate) — plus that every component subpath the core exports resolves back into itself. Verified by mutation: renaming a module in the manifest reddens three tests, dropping a directive reddens one.

  One more assertion keeps a docblock honest: the core still publishes no components/<Name>/styles.css, which is the whole reason importStyle defaults to false. Should that change, the default is to be revisited rather than left running on inertia.

• lint script and an ESLint config. This was the only package in the monorepo without either, so its sources were never linted — in CI or locally. The config matches granularity-datasource (Node + TypeScript, no Vue); vitest.config.ts joined tsconfig.json#include, without which typed rules cannot parse it. The first run found eight problems, all fixed. The root lint alias and the build-unplugin-granularity CI job run it now.

Changed

• Peer floors on @feugene/* raised to the current minor. Every peer this package declares on the ecosystem now starts at the version the monorepo actually ships:

  • @feugene/granularity → >=0.36.0 <1.0.0

  The floors had drifted far behind — some still admitted releases from a year of development ago — and a range that claims support it was never tested against is worse than a narrow one: the install succeeds and the breakage surfaces later, in the consumer’s app.

  This is breaking for anyone below a floor. Installing against an older @feugene/granularity now produces a peer conflict instead of silence. The fix is to move the core up; nothing in this package’s own API changed.

Fixed

• The package tarball now ships LICENSE. The manifest has always declared "license": "SEE LICENSE IN LICENSE", and the file it points at was not there: npm adds LICENSE to a tarball on its own, but only when the file exists in the package directory. A consumer’s compliance scanner reads a licence reference that resolves to nothing and flags the dependency as unlicensed — a refusal on formal grounds, before anyone reads the terms.

  The copy is byte-identical to the one at the repository root and is kept that way by yarn check:licenses, a gate in CI: eleven copies of a 598-line file drift silently, and they drift exactly when the licence text is being edited.

• The readme no longer calls the licence Apache-2.0. It is Apache License 2.0 plus an Additional Ethical Use Clause — a use restriction on top, which makes the licence source-available rather than OSI-approved open source. The readme ships inside the tarball and is what npm renders on the package page, so the claim was wrong in the one place a consumer is most likely to read it.

Behaviour change: importStyle is now off by default.

Fixed

• importStyle pointed at a stylesheet no component publishes. On by default, it added <pkg>/components/<Name>/styles.css as a side effect — a subpath the core does not export at all, so a consumer using the defaults hit ERR_PACKAGE_PATH_NOT_EXPORTED on every component, not on a rare one. Nothing inside this repository caught it: the showcase, the only consumer here, passes importStyle: false.

  It is off by default now, and for the core it is not needed at all: a component that has CSS of its own imports it from its own chunk (libInjectCss), and most components have none — their look is assembled by the UnoCSS preset from the components you select. The option stays for providers that ship CSS as separate files and declare them in exports.

Breaking for old cores: the peer range now starts at @feugene/granularity@0.28.2.

Fixed

• Parts of composite components resolved to a path no package published. The greedy Gr* resolver built @feugene/granularity/components/GrTimelineItem, while the package published a subpath only for components with their own index.ts and config.ts. Parts live in the parent’s directory, so a consumer’s build failed with "./components/GrTimelineItem" is not exported under the conditions — no type error, no warning, and only once the part actually appeared in a template. All twenty were affected: menu items, GrListItem, GrSidebarItem, GrTabPanel, the parts of GrDialog.

  Fixed in the core rather than here: @feugene/granularity@0.28.2 publishes a subpath alias for every part, so the plugin builds the path by name, the same way it does for any component, and carries no knowledge of what is composed of what. Hence the peer bump — on an older core those subpaths do not exist.

Added

• subcomponents on createGranularResolver — a map «part → owning component» for a provider that does not publish such aliases yet: the import, and the styles.css side effect with it, are taken from the owner’s subpath. Companion packages of the core no longer need it.

Fixed

• The documented default for prefix was wrong. The README said default 'Ds'; the resolver has defaulted to 'Gr' since the package was renamed, so anyone who trusted the README set a prefix they did not need.

Changed

• Examples point at @feugene/granularity-chrono. The companion package they referenced (@feugene/granularity-datepicker) has been removed from the repository, so every snippet, comment and test fixture named a package that no longer exists.

• The peer range on the core is >=0.12.0. It claimed >=0.11.0, while the resolver has needed the subpath layout introduced in 0.12.0 all along.

Added

• createGranularResolver — a generic unplugin-vue-components component-resolver factory for any granular package in the ecosystem (core or companion). Matches by prefix (greedy) or an explicit components whitelist, targets a configurable packageName, and optionally adds the per-component styles.css side-effect (importStyle, default false for CSS-inlined packages). Companion packages (e.g. @feugene/granularity-datepicker) build their own resolver on top of it.

Changed

• GranularityResolver is now implemented on top of createGranularResolver — no behavior change.