flipbookengine 0.5.3 → 0.6.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,33 +1,45 @@
1
- # Changelog
2
-
3
- ## 0.5.3
4
-
5
- - pinned the jsdom test dependency to a Node 18-compatible release so the full CI matrix runs consistently
6
-
7
-
8
-
9
- ## 0.5.2
10
-
11
- - restored the domwise project acknowledgement in the package README
12
- - kept commercial backend roadmap details separate from the open-source viewer documentation
13
-
14
-
15
-
16
- ## 0.5.1
17
-
18
- - removed maintainer-only npm publishing instructions from the package README
19
- - clarified the open-source viewer and commercial backend roadmap
20
-
21
-
22
-
23
- ## 0.5.0
24
-
25
- - added on-demand PDF page rendering with first-page readiness and next-page prefetch
26
- - added bounded per-instance PDF render cache via `pdfRenderCacheSize`
27
- - added React/Vue wrapper, browser E2E, and large-document regression coverage
28
- - added reduced-motion support for JavaScript page turns and CSS transitions
29
- - removed test exception suppression so asynchronous teardown failures surface
30
-
1
+ # Changelog
2
+
3
+ ## 0.6.0 (unreleased)
4
+
5
+ - added a localized, theme-aware Table of Contents panel with nested host-provided page entries
6
+ - added TOC visibility events, page navigation, normalization, accessibility, and regression tests
7
+
8
+ ## 0.5.4
9
+
10
+ - restored the modular FlipbookEngine source line after an unreleased post-0.5.3 source regression
11
+ - hardened engine lifecycle cleanup, locale API compatibility, and PDF render error propagation
12
+ - added regression coverage for the fixes above
13
+ - The published 0.5.3 package remains valid; upgrade to 0.5.4 or later for the fixes in this release. The post-tag source regression was not published to npm.
14
+
15
+ ## 0.5.3
16
+
17
+ - pinned the jsdom test dependency to a Node 18-compatible release so the full CI matrix runs consistently
18
+
19
+
20
+
21
+ ## 0.5.2
22
+
23
+ - restored the domwise project acknowledgement in the package README
24
+ - kept commercial backend roadmap details separate from the open-source viewer documentation
25
+
26
+
27
+
28
+ ## 0.5.1
29
+
30
+ - removed maintainer-only npm publishing instructions from the package README
31
+ - clarified the open-source viewer and commercial backend roadmap
32
+
33
+
34
+
35
+ ## 0.5.0
36
+
37
+ - added on-demand PDF page rendering with first-page readiness and next-page prefetch
38
+ - added bounded per-instance PDF render cache via `pdfRenderCacheSize`
39
+ - added React/Vue wrapper, browser E2E, and large-document regression coverage
40
+ - added reduced-motion support for JavaScript page turns and CSS transitions
41
+ - removed test exception suppression so asynchronous teardown failures surface
42
+
31
43
 
32
44
 
33
45
  ## 0.4.0
@@ -1,45 +1,45 @@
1
- # FlipbookEngine Commercial License
2
-
3
- Copyright (c) 2026 Murat Dogan
4
-
5
- This document describes the commercial licensing model for FlipbookEngine.
6
-
7
- ## When a Commercial License Is Required
8
-
9
- A commercial license is required if you use FlipbookEngine in any of the following:
10
-
11
- - closed-source or proprietary applications
12
- - SaaS, hosted, or managed platforms
13
- - client or agency delivery work
14
- - paid products or internal commercial systems where AGPL obligations are not acceptable
15
-
16
- ## Commercial License Scope
17
-
18
- A commercial license may grant rights such as:
19
-
20
- - use in proprietary software
21
- - redistribution as part of a larger commercial product
22
- - internal modification for business needs
23
- - deployment in hosted commercial environments
24
-
25
- The exact scope, support level, update access, warranty, and pricing are defined in the commercial agreement signed with the licensor.
26
-
27
- ## Restrictions
28
-
29
- Without a specific written commercial agreement, you may not:
30
-
31
- - resell FlipbookEngine itself as a competing flipbook engine product
32
- - sublicense the engine as your own standalone engine
33
- - remove copyright, attribution, or licensing notices required by agreement
34
- - claim ownership of the original software or brand
35
-
36
- ## Support
37
-
38
- Commercial support, SLAs, onboarding, or custom development are available only if explicitly included in a paid agreement.
39
-
40
- ## Contact
41
-
42
- Commercial licensing and partnership inquiries:
43
-
44
- - murat.dogan@hotmail.com.tr
45
-
1
+ # FlipbookEngine Commercial License
2
+
3
+ Copyright (c) 2026 Murat Dogan
4
+
5
+ This document describes the commercial licensing model for FlipbookEngine.
6
+
7
+ ## When a Commercial License Is Required
8
+
9
+ A commercial license is required if you use FlipbookEngine in any of the following:
10
+
11
+ - closed-source or proprietary applications
12
+ - SaaS, hosted, or managed platforms
13
+ - client or agency delivery work
14
+ - paid products or internal commercial systems where AGPL obligations are not acceptable
15
+
16
+ ## Commercial License Scope
17
+
18
+ A commercial license may grant rights such as:
19
+
20
+ - use in proprietary software
21
+ - redistribution as part of a larger commercial product
22
+ - internal modification for business needs
23
+ - deployment in hosted commercial environments
24
+
25
+ The exact scope, support level, update access, warranty, and pricing are defined in the commercial agreement signed with the licensor.
26
+
27
+ ## Restrictions
28
+
29
+ Without a specific written commercial agreement, you may not:
30
+
31
+ - resell FlipbookEngine itself as a competing flipbook engine product
32
+ - sublicense the engine as your own standalone engine
33
+ - remove copyright, attribution, or licensing notices required by agreement
34
+ - claim ownership of the original software or brand
35
+
36
+ ## Support
37
+
38
+ Commercial support, SLAs, onboarding, or custom development are available only if explicitly included in a paid agreement.
39
+
40
+ ## Contact
41
+
42
+ Commercial licensing and partnership inquiries:
43
+
44
+ - murat.dogan@hotmail.com.tr
45
+