Skip to content
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

Side effect imports don't report non-existent paths #2001

Open
sodic opened this issue May 2, 2024 · 1 comment
Open

Side effect imports don't report non-existent paths #2001

sodic opened this issue May 2, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@sodic
Copy link
Contributor

sodic commented May 2, 2024

Steps to reproduce:

  1. Go into a Wasp app (I tried waspc/todoApp).

  2. Add a side-effect import of something that doesn't exist (I tried it in the client code, don't know about the server):

    import 'something'
    // rest of code
  3. Witness the lack of an error.

@sodic sodic added the bug Something isn't working label May 2, 2024
@sodic
Copy link
Contributor Author

sodic commented May 2, 2024

@infomiho believes this is caused by Vite.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant