Skip to content

Removed reference to js/ts toggle. #13717

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 15, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -55,7 +55,7 @@ The `src` directory contains the meat of your project. Everything except `src/ro
- `hooks.server.js` contains your server [hooks](hooks)
- `service-worker.js` contains your [service worker](service-workers)

(Whether the project contains `.js` or `.ts` files depends on whether you opt to use TypeScript when you create your project. You can switch between JavaScript and TypeScript in the documentation using the toggle at the bottom of this page.)
(Whether the project contains `.js` or `.ts` files depends on whether you opt to use TypeScript when you create your project.)

If you added [Vitest](https://vitest.dev) when you set up your project, your unit tests will live in the `src` directory with a `.test.js` extension.


Unchanged files with check annotations Beta

test.describe('Filesystem updates', () => {
if (process.env.DEV) {
test('New route is immediately available in dev', async ({ page }) => {

Check warning on line 14 in packages/kit/test/apps/writes/test/test.js

GitHub Actions / test-kit (22, ubuntu-latest, chromium)

flaky test: New route is immediately available in dev

retries: 2

Check warning on line 14 in packages/kit/test/apps/writes/test/test.js

GitHub Actions / test-kit (18, ubuntu-latest, chromium)

flaky test: New route is immediately available in dev

retries: 2

Check warning on line 14 in packages/kit/test/apps/writes/test/test.js

GitHub Actions / test-kit (20, ubuntu-latest, chromium)

flaky test: New route is immediately available in dev

retries: 2
await page.goto('/new-route');
// hash the filename so that it won't conflict with
test.describe.configure({ mode: 'parallel' });
test.describe('a11y', () => {
test('resets focus', async ({ page, clicknav, browserName }) => {

Check warning on line 12 in packages/kit/test/apps/basics/test/cross-platform/client.test.js

GitHub Actions / test-kit-cross-browser (18, windows-2019, chromium, dev)

flaky test: resets focus

retries: 2
const tab = browserName === 'webkit' ? 'Alt+Tab' : 'Tab';
await page.goto('/accessibility/a');
expect(await page.evaluate(() => document.documentElement.getAttribute('tabindex'))).toBe(null);
});
test('applies autofocus after a navigation', async ({ page, clicknav }) => {

Check warning on line 36 in packages/kit/test/apps/basics/test/cross-platform/client.test.js

GitHub Actions / test-kit-cross-browser (18, windows-2019, chromium, dev)

flaky test: applies autofocus after a navigation

retries: 2
await page.goto('/accessibility/autofocus/a');
await clicknav('[href="/accessibility/autofocus/b"]');
await expect(page.locator('h1')).toHaveText('target: 1');
});
test('responds to <form method="GET"> submission without reload', async ({ page }) => {

Check warning on line 870 in packages/kit/test/apps/basics/test/cross-platform/client.test.js

GitHub Actions / test-kit-server-side-route-resolution (build)

flaky test: responds to <form method="GET"> submission without reload

retries: 2
await page.goto('/routing/form-get');
expect(await page.textContent('h1')).toBe('...');