flipbookengine 0.5.3 → 0.5.4

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,5 +1,12 @@
1
1
  # Changelog
2
2
 
3
+ ## 0.5.4
4
+
5
+ - restored the modular FlipbookEngine source line after an unreleased post-0.5.3 source regression
6
+ - hardened engine lifecycle cleanup, locale API compatibility, and PDF render error propagation
7
+ - added regression coverage for the fixes above
8
+ - 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.
9
+
3
10
  ## 0.5.3
4
11
 
5
12
  - pinned the jsdom test dependency to a Node 18-compatible release so the full CI matrix runs consistently
@@ -28,23 +35,23 @@
28
35
  - added reduced-motion support for JavaScript page turns and CSS transitions
29
36
  - removed test exception suppression so asynchronous teardown failures surface
30
37
 
31
-
32
-
33
- ## 0.4.0
34
-
35
- - externalized PDF.js as an npm dependency with consumer-provided worker configuration
36
- - fixed PDF-only initialization when `pages` is omitted
37
- - isolated engine state and lifecycle cancellation per instance
38
- - aligned framework wrappers, events, options, fullscreen, audio, and download controls
39
- - added progressive image quality loading and bounded PDF rendering with cancellation
40
- - added accessibility semantics, structured PDF progress/error events, and expanded regression tests
41
- - added CI dependency audit, reproducible package verification, and provenance-enabled release workflow
42
-
43
- ## 0.1.0
44
-
45
- - renamed public product identity to FlipbookEngine
46
- - introduced dual-license documentation structure
47
- - prepared package metadata for public distribution
48
- - preserved legacy `BizekaFlipEngine` compatibility alias
49
- - added contribution, security, and trademark policy documents
50
-
38
+
39
+
40
+ ## 0.4.0
41
+
42
+ - externalized PDF.js as an npm dependency with consumer-provided worker configuration
43
+ - fixed PDF-only initialization when `pages` is omitted
44
+ - isolated engine state and lifecycle cancellation per instance
45
+ - aligned framework wrappers, events, options, fullscreen, audio, and download controls
46
+ - added progressive image quality loading and bounded PDF rendering with cancellation
47
+ - added accessibility semantics, structured PDF progress/error events, and expanded regression tests
48
+ - added CI dependency audit, reproducible package verification, and provenance-enabled release workflow
49
+
50
+ ## 0.1.0
51
+
52
+ - renamed public product identity to FlipbookEngine
53
+ - introduced dual-license documentation structure
54
+ - prepared package metadata for public distribution
55
+ - preserved legacy `BizekaFlipEngine` compatibility alias
56
+ - added contribution, security, and trademark policy documents
57
+
@@ -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
+