Skip to content

Feat: rsvelte - #3

Draft
darbymanning wants to merge 1 commit into
mainfrom
rsvelte
Draft

Feat: rsvelte#3
darbymanning wants to merge 1 commit into
mainfrom
rsvelte

Conversation

@darbymanning

Copy link
Copy Markdown
Collaborator

No description provided.

…ct updated add-ons, and replace ESLint with rsvelte tools in package.json for improved linting and formatting. Remove eslint.config.js and adjust README.md to highlight new tooling. Update vite.config.ts for compatibility with rsvelte's dynamic compile options and enhance VSCode settings for Svelte file formatting.
<div class="details" transition:slide>
We use cookies to improve your experience.<br />"Essential" cookies are needed for the site to
function.
We use cookies to improve your experience.<br />"Essential" cookies are needed for the site to function.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Curious on this diff, do we need to change line width or was this previously formatted incorrectly?

Comment thread src/hooks.server.ts
export function handleError({ error }) {
import type { Handle, HandleServerError } from '@sveltejs/kit'

export const handleError: HandleServerError = ({ error }) => {

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I always dislike this added ceremony (explicitly importing types that SvelteKit has already typed through its magic 🪄)

I can either learn to embrace types everywhere even though its already typesafe, for the sake of being explicit (good argument for it) - or, can we revert this as the types are already applied?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants