6adaf56c73
* added value rules * resolved errors raised by vale * added github action * fixes to github action * added details in contribution guidelines * added rule for numbers * limited checks to errors
34 lines
1.1 KiB
Markdown
34 lines
1.1 KiB
Markdown
# v1.3.8
|
||
|
||
Updating your medusa server to version `1.3.8` may cause issues when using NPM. Please refer to this guide for more details on how to resolve it.
|
||
|
||
## Update Using Yarn
|
||
|
||
It's highly recommended to use [yarn](https://yarnpkg.com/) when working with Medusa. Updating with yarn should resolve any issues you might run into during the update.
|
||
|
||
## Resolving Update Issues with NPM
|
||
|
||
### Update All Medusa Dependencies
|
||
|
||
If you face any errors during your update to version `1.3.8`, make sure to update all Medusa dependencies you’re using on your server. This includes `medusa-interfaces`, `@medusajs/medusa-cli`, or any of Medusa’s official plugins.
|
||
|
||
You can update to the latest version of these using the `@latest` version tag. For example:
|
||
|
||
```bash
|
||
npm install medusa-interfaces@latest
|
||
```
|
||
|
||
### Use Legacy Peer Dependencies Option
|
||
|
||
:::caution
|
||
|
||
This solution can be used as a workaround and should be used with caution to avoid any issues while using Medusa.
|
||
|
||
:::
|
||
|
||
If all fails, you can use the `--legacy-peer-deps` option while updating Medusa:
|
||
|
||
```bash
|
||
npm install @medusajs/medusa@latest --legacy-peer-deps
|
||
```
|