chore(deps,docs): split docs toolchain from core package and modernize build deps#173
Merged
elreco merged 1 commit intoelreco:mainfrom Feb 11, 2026
Merged
Conversation
|
@ignatremizov is attempting to deploy a commit to the ELRECO Team on Vercel. A member of the Team first needs to authorize it. |
…e build dependencies Separate documentation build dependencies from the library package so root installs and audits only reflect runtime/build requirements of the published component, while also upgrading the core toolchain to current versions that work on Node 24. Problem: - Root dependency graph included VitePress/docs-only packages, causing audit noise unrelated to the published library. - Forced audit upgrades left the tree inconsistent (including an accidental docs stack downgrade), and newer vite-plugin-dts exposed a private Props type in declaration rollup. Approach: - Isolate docs tooling into docs/package.json and route docs scripts through npm --prefix docs. - Upgrade core dev toolchain to a coherent modern baseline (Vite 7, vite-plugin-dts 4, semantic-release 25, updated plugin/dependency set). - Apply minimal source compatibility fix for d.ts generation by exporting Props from VueTailwindDatePicker. Changes: - Move VitePress and docs PostCSS stack out of root into docs/package.json with its own lockfile. - Update root scripts: docs:dev/docs:build/docs:serve now execute in docs package. - Remove commitizen/cz tooling from root package to reduce security surface and unused dev dependencies. - Upgrade and align root dependencies: vite, @vitejs/plugin-vue, vite-plugin-dts, semantic-release family, commitlint, tailwind/dayjs/vue/fs-extra, and related lockfile updates. - Reorder package exports conditions so types is evaluated before import/require (removes Vite 7 warning). - Export Props interface in src/VueTailwindDatePicker.vue to satisfy vite-plugin-dts rollup type checks. Tests: - npm audit (root): found 0 vulnerabilities. - npm run typecheck: pass. - npm run build: pass. - npm run docs:build: pass (using docs package). Behavioral effect: - Library runtime behavior is unchanged. - Documentation tooling is now isolated from core package installs/audits. - Builds continue to emit the existing API Extractor TypeScript version notice only (informational).
ignatremizov
force-pushed
the
chore/split-docs-toolchain
branch
from
e735b77 to
82bef8d
Compare
elreco
approved these changes
Feb 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
docs/package.jsonanddocs/package-lock.jsonnpm --prefix docsvite@7,vite-plugin-dts@4,semantic-release@25family,commitlint@20, updated Vue/Tailwind/dayjs/fs-extra)Propsfromsrc/VueTailwindDatePicker.vueto satisfy declaration rollup checks withvite-plugin-dts@4package.jsonexportsconditions (typesbeforeimport/require) to removevite@7warningoverflow-hiddenin left panel wrappers)Why
vitepress) were polluting rootnpm auditresults even though they are not part of the published library runtime/build pathValidation
npm audit(root):0 vulnerabilitiesnpm run typecheck: passnpm run build: passnpm run docs:build: passNotes
build still emits API Extractor TypeScript version notice (bundled
5.8.2vs project5.9.x); informational only, no build/typecheck failureupstream tracking for this warning: Bump TypeScript to 5.9. microsoft/rushstack#5550