From 6a18b6c8f3bf52c0840dcaeb26af5ef612b55246 Mon Sep 17 00:00:00 2001 From: Hector Hernandez <39923391+hectorhdzg@users.noreply.github.com> Date: Wed, 27 May 2026 16:39:11 -0700 Subject: [PATCH] fix: restore tools/rollup in published package and bump to 2.0.5 The Rush removal (dc4e848) changed rollup/tsconfig.json to output locally instead of into lib/tools/rollup/, causing the tools/rollup directory to be empty at pack time. This broke consumers using @microsoft/dynamicproto-js/tools/rollup. Changes: - Revert rollup/tsconfig.json outDir/declarationDir to ../lib/tools/rollup/ - Revert lib/rollup.config.js import to ./tools/rollup/dist-es5/removeDynamic - Add build:rollup-bundle step to produce ESM/Node bundles and copy package.json - Bump version to 2.0.5 --- RELEASES.md | 11 ++++++++++- docs/typedoc/functions/default.html | 4 ++-- docs/typedoc/interfaces/idynamicprotoopts.html | 6 +++--- lib/package.json | 2 +- lib/rollup.config.js | 2 +- package.json | 5 +++-- rollup/tsconfig.json | 4 ++-- 7 files changed, 22 insertions(+), 12 deletions(-) diff --git a/RELEASES.md b/RELEASES.md index 283788d..4f21b35 100644 --- a/RELEASES.md +++ b/RELEASES.md @@ -1,6 +1,15 @@ # Releases -## 2.0.4 (TBD) +## 2.0.5 (May 27th, 2026) + +### Bug Fix + +- Fix `tools/rollup` directory missing from published npm package since 2.0.4 + - Restore TypeScript output paths for rollup plugin to `lib/tools/rollup/` + - Add rollup bundle step to produce ESM/Node formats for the rollup plugin + - Ensures `@microsoft/dynamicproto-js/tools/rollup` is available to consumers + +## 2.0.4 (May 27th, 2026) ### Changes diff --git a/docs/typedoc/functions/default.html b/docs/typedoc/functions/default.html index ecf3db2..5fd70e7 100644 --- a/docs/typedoc/functions/default.html +++ b/docs/typedoc/functions/default.html @@ -18,8 +18,8 @@
Optionaloptions: IDynamicProtoOptsExposes the default global options to allow global configuration, if the global values are disabled these will override any passed values. This is primarily exposed to support unit-testing without the need for individual classes to expose their internal usage of dynamic proto.
-
Additional options to configure how the dynamic prototype operates