sveltejs/svelte.dev

Following the tutorial there are minor annoyances

Open

#1,657 opened on Nov 9, 2025

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Svelte (255 forks)github user discovery
help wanted

Repository metrics

Stars
 (301 stars)
PR merge metrics
 (PR metrics pending)

Description

Describe the bug

  1. After clicking solve for https://svelte.dev/tutorial/kit/the-form-element there is bunch of compiler warnings regarding unused scss.
  1. When trying to create a file under https://svelte.dev/tutorial/kit/pages I mistakenly enetered *page.svelte instead of +page.svelte and I got unclear warning about what my mistake is.
  1. I have a dark theme set on my mac, and the tutorial page seems to reflect it. Once i add a ToDo in https://svelte.dev/tutorial/kit/form-validation the page changes to 'normal' mode and background is white instead of gray.

Those are minor annoyance but could be definitely improved. I found the tutorial cool , but such small things make a tutorial look less professional than it is. Once i find more time during the week I will try to fix them myself.

Reproduction

Reproduction steps above

Logs

System Info

MacOS 26.0.1 
No specific info, those infos are relevant to tutorial

Severity

annoyance

Additional Information

Tested on brave browser

Contributor guide

Research direction
Investigate the three issues: (1) locate where SCSS is imported in the tutorial and find the unused variables causing compiler warnings; (2) find the file creation validation logic and improve the error message for invalid file names; (3) check the tutorial's theme handling to ensure it respects system preferences consistently.
Tech stack
svelte
Domain
documentationfrontend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Svelte
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75