update and lint fixes

[gustavocodess]

Description

Add a short description of what changes you made, why you made them, and any other context that you think might be helpful for someone to better understand what is contained in this pull request. This sort of information is useful for people reviewing the code, as well as anyone from the future trying to understand why changes were made or why a bug started happening.

Screenshot If relevant, add a screenshot or two of the changes you made.

[Dkendal]

Needs a PR description, what does "update" mean here?

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
svelte-vite-example	✅ Ready (Inspect)	Visit Preview	Sep 13, 2022 at 3:21PM (UTC)

[gitguardian[bot]]

⚠️ GitGuardian has uncovered 6 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	Secret	Commit	Filename
-	Generic High Entropy Secret	6ffa5402be6f9d235a69e4e8f3cd1ec27c8457c6	packages/sdks/e2e/tests/specs/data-bindings.ts	View secret
-	Generic High Entropy Secret	6ffa5402be6f9d235a69e4e8f3cd1ec27c8457c6	packages/sdks/e2e/tests/specs/symbols.ts	View secret
-	Generic High Entropy Secret	6ffa5402be6f9d235a69e4e8f3cd1ec27c8457c6	packages/sdks/e2e/tests/specs/symbols.ts	View secret
-	Generic High Entropy Secret	6ffa5402be6f9d235a69e4e8f3cd1ec27c8457c6	packages/sdks/e2e/tests/specs/symbols.ts	View secret
-	Generic High Entropy Secret	6ffa5402be6f9d235a69e4e8f3cd1ec27c8457c6	packages/sdks/e2e/tests/specs/symbols.ts	View secret
-	Generic High Entropy Secret	6ffa5402be6f9d235a69e4e8f3cd1ec27c8457c6	packages/sdks/e2e/tests/specs/symbols.ts	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

<sup>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sup>