Skip to content

Commit 9a2e0d1

Browse files
authored
release: Amplify JS release (#13921)
2 parents 4595dae + 5c3f17a commit 9a2e0d1

File tree

17 files changed

+2155
-2174
lines changed

17 files changed

+2155
-2174
lines changed

.eslintrc.js

-186
This file was deleted.

CONTRIBUTING.md

+10
Original file line numberDiff line numberDiff line change
@@ -126,6 +126,16 @@ In your sample project, you can now link specific packages
126126
yarn link @aws-amplify/auth
127127
```
128128

129+
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 `yarn run dev`, Vite caching may be the culprit. Try editing this line in your sample project's `package.json`.
130+
131+
```diff
132+
"scripts": {
133+
- "dev": "vite",
134+
+ "dev": "vite --force",
135+
...
136+
}
137+
```
138+
129139
Passing unit tests are only necessary if you’re looking to contribute a pull request. If you’re just playing locally, you don’t need them. However, if you’re contributing a pull request for anything other than making a change to the documentation, fixing a formatting issue in the code (i.e., white space, missing semi-colons) or another task that does not impact the functionality of the code, you will need to validate your proposed changes with passing unit tests.
130140

131141
#### Verdaccio

0 commit comments

Comments
 (0)