fix(CssManager): Make CssManager a singleton and export the shared instance via getSingleton; update tests and dependencies
This commit is contained in:
@@ -1,5 +1,14 @@
|
||||
# Changelog
|
||||
|
||||
## 2025-11-16 - 2.1.3 - fix(CssManager)
|
||||
Make CssManager a singleton and export the shared instance via getSingleton; update tests and dependencies
|
||||
|
||||
- Convert CssManager to a singleton by adding a private static instance and a public static getSingleton() method.
|
||||
- Use CssManager.getSingleton() for the exported cssManager in ts/index.ts to ensure a single shared instance across the app.
|
||||
- Add a Chromium-focused test (test.chromium.ts) and remove the browser-specific test file.
|
||||
- Bump devDependencies (@git.zone/tsbuild, @git.zone/tsbundle, @git.zone/tstest) and update lit to ^3.3.1.
|
||||
- Add readme.hints.md documenting the CssManager singleton pattern and supported access patterns.
|
||||
|
||||
## 2025-07-06 - 2.1.2 - fix(build)
|
||||
Update build script in package.json to include 'tsfolders' in tsbuild command
|
||||
|
||||
|
||||
Reference in New Issue
Block a user