component-template VS jest-dom

Reason I'm asking is that the official component template has a build step that compiles it to pure js. But I just tried publishing it with no build step (so literally just button.svelte, index.mjs and package.json and it seems to work fine.

But what would it be like to build your own Svelte component library? Fortunately, there are several templates that you could start with, like the official template provided by Svelte and Svelte 3 Component Template, which are considered the go-to for building your own component library.

My question is: is there a good up-to-date Tailwind, Svelte, Storybook template out there? The one on Github is pretty old and was abandoned 5+ months ago. With the pace of change, I'm worried I'd bump into legacy bugs. I'm confused as to where to start because Svelte has an official component-template but its 10 months old. Also, which bundler is the best for a newbie? Lastly, should I use svelte-add or is there a more stable solution out there with support for Storybook?

The official component template still has an open issue pertaining typescript support, and there's several templates linked there. Given that time is a rare resource, and given that I frankly don't trust myself to make the right decision here up-front, I'd be interested in your thoughts and experiences. Are there trade-offs in the available TS templates? Or does one of them basically tick all the boxes already? If so, why is there no endorsed official TS template?

//config/jest/setupTests.ts // jest-dom adds custom jest matchers for asserting on DOM nodes. // allows you to do things like: // expect(element).toHaveTextContent(/react/i) // learn more: https://github.com/testing-library/jest-dom import '@testing-library/jest-dom';

Update: Just got it working. Following the instructions on this github issue and using `shamefully-hoist=true` with pnpm I got it working. The issue I was facing was with pnpm.

React Testing Library uses jest-dom which has a .getByText() matcher.

vitest-dom extends the standard Jest matchers with convenient methods like .toBeDisabled. Now you can write tests that assert on the state of the DOM. The package is a fork of @testing-library/jest-dom.

jest-dom matchers

At the time of writing this article, it still seems to be an open issue. However, a workaround I found is to add "skipLibCheck": true, to your tsconfig.json file.

// jest-dom adds custom jest matchers for asserting on DOM nodes. // allows you to do things like: // expect(element).toHaveTextContent(/react/i) // learn more: https://github.com/testing-library/jest-dom import '@testing-library/jest-dom'; import { server } from './mocks/server'; beforeAll( () => server.listen( { onUnhandledRequest: 'error' } ) ); afterEach( () => server.resetHandlers() ); afterAll( () => server.close() );

Everything you want to do to your test environment such as extends the jest matchers with @testing-library/jest-dom, mock some APIs that’s not implemented in jdom, you can put to config/jest/setupTests.js:

This will register the additional assertions from @testing-library/jest-dom.