Upgrade to svelte 4 x x

.github/FUNDING.yml

@@ -1,9 +1,3 @@
-# These are supported funding model platforms
-
-
-github:
- - Alia5
-custom:
- - https://www.buymeacoffee.com/flatspotso7
- - https://www.paypal.com/donate/?hosted_button_id=TDKKBV7QU67L6
- - https://paypal.me/flatspotpics
+github: [MelleD]
+buy_me_a_coffee: melled
+custom: ["https://www.paypal.me/MelleDennis"]

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,34 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: bug
+assignees: ''
+---
+
+READ THIS FIRST:
+Thanks for raising a expander card issue. Please take the time to review the following
+categories as some of them do not apply here.
+
+🙅 "Please DO NOT Raise an Issue" Cases
+- Question
+STOP!! Please ask questions about how to use something, or to understand why something isn't
+working as you expect it to Github discussion or on forum https://community.home-assistant.io/t/expander-accordion-collapsible-card/738817/4.
+- Managed Dependency Upgrade
+You DO NOT need to raise an issue for a managed dependency version upgrade as there's a semi-automatic process for checking managed dependencies for new versions before a release. BUT pull requests for upgrades that are more involved than just a version property change are still most welcome.
+- With an Immediate Pull Request
+An issue will be closed as a duplicate of the immediate pull request, so you don't have to raise an issue if you plan to create a pull request immediately.
+
+🐞 Bug report (please don't include this emoji/text, just add your details)
+Please provide details of the problem, including the version of expander card and your Brwoser that you
+are using. If possible, please provide a test case or sample application that reproduces
+the problem. This makes it much easier for us to diagnose the problem and to verify that
+we have fixed it
+For quick troubleshooting, prepare a [minimally reproducible example](https://en.wikipedia.org/wiki/Minimal_reproducible_example).
+
+!!!Please check your Browser console for Javascript errors!!!
+
+
+
+TIP: You can always edit your issue if it isn't formatted correctly.
+     See https://guides.github.com/features/mastering-markdown 

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,25 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: feature request
+assignees: ''
+---
+
+**Is your feature request related to a problem? Please describe.**
+Please start by describing the problem that you are trying to solve. There may already
+be a solution, or there may be a way to solve it that you hadn't considered.
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.
+
+
+TIP: You can always edit your issue if it isn't formatted correctly.
+     See https://guides.github.com/features/mastering-markdown 

.github/dependabot.yml

@@ -0,0 +1,14 @@
+# To get started with Dependabot version updates, you'll need to specify which
+# package ecosystems to update and where the package manifests are located.
+# Please see the documentation for all configuration options:
+# https://docs.github.com/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file
+
+version: 2
+updates:
+  # Enable version updates for npm
+  - package-ecosystem: "npm"
+    # Look for `package.json` and `lock` files in the `root` directory
+    directory: "/"
+    # Check the npm registry for updates every day (weekdays)
+    schedule:
+      interval: "daily"

.github/release.yml

@@ -3,6 +3,9 @@ changelog:
     - title: 🛠 Dependency Upgrades 
       labels:
         - dependencies
+    - title: 🐛 Bug fixes
+      labels:
+        - bug
     - title: ⭐ New Features
       labels:
         - "*"

.github/workflows/autoClose.yml

@@ -0,0 +1,23 @@
+name: Close inactive issues
+on:
+  schedule:
+    - cron: "30 1 * * *"
+
+jobs:
+  close-issues:
+    runs-on: ubuntu-latest
+    permissions:
+      issues: write
+      pull-requests: write
+    steps:
+      - uses: actions/stale@v5
+        with:
+          days-before-issue-stale: 30
+          days-before-issue-close: 14
+          stale-issue-label: "stale"
+          stale-issue-message: "This issue is stale because it has been open for 30 days with no activity."
+          close-issue-message: "This issue was closed because it has been inactive for 14 days since being marked as stale."
+          days-before-pr-stale: -1
+          days-before-pr-close: -1
+          repo-token: ${{ secrets.GITHUB_TOKEN }}
+          only-labels: "wait-for-user-input,wait-for-mre"