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

chore: update contributing guide vite troubleshooting #13826

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

scanlonp
Copy link

My library changes were not showing up in my locally deployed app. Vite caching turned out to be the issue. Add a note to help future contributors avoid this problem.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@scanlonp scanlonp requested a review from a team as a code owner September 18, 2024 20:54
@HuiSF HuiSF changed the title docs: update contributing guide vite troubleshooting chore: update contributing guide vite troubleshooting Sep 18, 2024
CONTRIBUTING.md Outdated
@@ -126,6 +126,16 @@ In your sample project, you can now link specific packages
yarn link @aws-amplify/auth
```

If you are testing with a Vite sample project, such as from the quickstart guide, and your changes to the library are not showing up in your local app when running `npm run dev`, Vite caching may be the culprit. Try editing this line in your sample project's `package.json`.
Copy link
Member

Choose a reason for hiding this comment

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

One recommendation, pretty much everywhere else in the contributing guide refers to using yarn as the package manager, so it's probably a good idea to keep it consistent.

Copy link
Author

Choose a reason for hiding this comment

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

Good call out. The quickstart guide uses npm, but there is no difference in behavior. I'll add that.

CONTRIBUTING.md Outdated Show resolved Hide resolved
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.

5 participants