Skip to content

Conversation

@FranjoMindek
Copy link
Contributor

@FranjoMindek FranjoMindek commented Dec 18, 2025

Description

I've removed jest-dom types from the SDK tsconfig because we no longer require it since moving jest-dom types to vite-end.d.ts file: https://github.com/wasp-lang/wasp/pull/2656/files

Full tested table:
vite - import '@testing-library/jest-dom' present in src/vite-env.d.ts.
sdk - testing-library/jest-dom present in sdk/wasp/tsconfig.json's types field.
user - node_modules/@testing-library present in ./tsconfig.json's typeRoots field of user's tsconfig.
compiles - wasp compile
IDE - editor support, no "red squiggly lines"

vite sdk user compiles IDE note
← state before #2656 PR
← current state
← the change I'm making
runtime error (wasp start)
can't compile
can't compile

Type of change

  • 🔧 Just code/docs improvement
  • 🐞 Bug fix
  • 🚀 New/improved feature
  • 💥 Breaking change

Checklist

  • I tested my change in a Wasp app to verify that it works as intended.

  • 🧪 Tests and apps:

    • I added unit tests for my change.
    • (if you fixed a bug) I added a regression test for the bug I fixed.
    • (if you added/updated a feature) I added/updated e2e tests in examples/kitchen-sink/e2e-tests.
    • (if you added/updated a feature) I updated the starter templates in waspc/data/Cli/templates, as needed.
    • (if you added/updated a feature) I updated the example apps in examples/, as needed.
      • (if you updated examples/tutorials) I updated the tutorial in the docs (and vice versa).
  • 📜 Documentation:

    • (if you added/updated a feature) I added/updated the documentation in web/docs/.
  • 🆕 Changelog: (if change is more than just code/docs improvement)

    • I updated waspc/ChangeLog.md with a user-friendly description of the change.
    • (if you did a breaking change) I added a step to the current migration guide in web/docs/migration-guides/.
    • I bumped the version in waspc/waspc.cabal to reflect the changes I introduced.

@pkg-pr-new
Copy link

pkg-pr-new bot commented Dec 18, 2025

Open in StackBlitz

@wasp.sh/wasp-cli

npx https://pkg.pr.new/wasp-lang/wasp/@wasp.sh/wasp-cli@3522

@wasp.sh/wasp-cli-darwin-arm64-unknown

npx https://pkg.pr.new/wasp-lang/wasp/@wasp.sh/wasp-cli-darwin-arm64-unknown@3522

@wasp.sh/wasp-cli-darwin-x64-unknown

npx https://pkg.pr.new/wasp-lang/wasp/@wasp.sh/wasp-cli-darwin-x64-unknown@3522

@wasp.sh/wasp-cli-linux-x64-glibc

npx https://pkg.pr.new/wasp-lang/wasp/@wasp.sh/wasp-cli-linux-x64-glibc@3522

@wasp.sh/wasp-cli-linux-x64-musl

npx https://pkg.pr.new/wasp-lang/wasp/@wasp.sh/wasp-cli-linux-x64-musl@3522

commit: 98c48d5

Copy link
Member

@cprecioso cprecioso left a comment

Choose a reason for hiding this comment

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

Change looks fine, but I'm not sure what the table refers to

EDIT: Sent it as "request changes" but I only wanted to send a "comment"

@cprecioso cprecioso self-requested a review December 19, 2025 13:40
Copy link
Member

@cprecioso cprecioso left a comment

Choose a reason for hiding this comment

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

LGTM and makes sense to me. I see CI passes so feels fine. Good job.

I understand a changelog entry is not required since this is not a user-facing change, right? However, if it's solving any issue or bug it'd be nice to have it there.

@FranjoMindek
Copy link
Contributor Author

It's not solving anything user facing, we just had extra stuff in SDK we didn't really need. That's why I'm keeping it undocumented.

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.

3 participants