svelteesp32

• Bug Fixes
  Resolved an error that occurred when '@' was included in file names, enhancing overall application functionality.

• Chores
  Updated various development dependencies to their latest versions for improved performance and security.

• New Features

  • Introduced support for a new engine type, psychic2, enhancing functionality for PsychicHttp v2.
  • Added a new command-line option for psychic2, allowing for additional configurations.
  • Implemented a new PsychicHttpServer setup for the PSYCHIC2 platform.

• Bug Fixes

  • Updated dependencies and scripts to improve performance and resolve potential issues.

• Documentation

  • Enhanced README to clarify support for PsychicHttp v2 and updated command line options.

• Chores

  • Incremented package version to 1.5.0 and updated related dependencies.

• New Features

  • Enhanced HTTP response handling by adding a "cache-control" header to improve content freshness.

• Bug Fixes

  • Resolved issues related to caching, ensuring more accurate responses based on ETag conditions.

New Features

• Implemented a new function to identify and log files with identical content.

Improvements

• Enhanced file processing by transitioning to a structured approach using a Map for better clarity and efficiency.
• Streamlined output formatting in logging functions to remove unnecessary whitespace.
• Added support for multiple linting tools to ensure higher code standards.
• Introduced a new configuration file for project settings, enhancing project management and code quality through automated reviews and integrations.

Bug Fixes

• Potential bug fixes included in the updated ESLint packages.

• feat: etag compiler option
• feat: gzip compiler option
• feat: order of directives
• feat: created and version info
• fix: separated demo env
• feat: create output directory
• feat: 2x9 build and test system
• feat: detect precompressed files
• feat: reduce .h file size
• feat: skip gz under 1024
• fix: pipeline node version
• fix: proper svelte demo app
• feat: warning if not usable directive used
• feat: colored console

• feat: filename directives are uppercased
• feat: filecount by extension
• fix: readme

Should we be able to check if a given file name or number of files is correct?
For this, we should find C++ defines in the generated code.