docs: change module paths in resolve (#7539)
Change the path to modules in the resolve property across docs
This commit is contained in:
@@ -121,10 +121,9 @@ The queries performed in each of the methods use PostgreSQL syntax.
|
||||
|
||||
### Run Migration
|
||||
|
||||
To reflect the changes in the migration, transpile your source files using the `build` command, then run the `migration` command:
|
||||
To reflect the changes in the migration, run the `migration` command:
|
||||
|
||||
```bash npm2yarn
|
||||
npm run build
|
||||
npx medusa migrations run
|
||||
```
|
||||
|
||||
|
||||
@@ -75,13 +75,7 @@ module.exports = defineConfig({
|
||||
|
||||
Its key (`helloModuleService`) is the name of the module’s main service. It will be registered in the Medusa container with that name.
|
||||
|
||||
Its value is an object having the `resolve` property, whose value is either a path to the directory holding the module or an `npm` package’s name.
|
||||
|
||||
<Note title="Tip">
|
||||
|
||||
When you run the `build` or `dev` command, your customizations are transpiled from the `src` directory into the `dist` directory. So, you point to the module in the `dist` directory.
|
||||
|
||||
</Note>
|
||||
Its value is an object having the `resolve` property, whose value is either a path to module's directory (relative to `src`, so it shouldn't include `src` in the path) or an `npm` package’s name.
|
||||
|
||||
### 4. Test the Module
|
||||
|
||||
|
||||
@@ -63,7 +63,7 @@ module.exports = defineConfig({
|
||||
options: {
|
||||
providers: [
|
||||
{
|
||||
resolve: "./dist/modules/my-fulfillment",
|
||||
resolve: "./modules/my-fulfillment",
|
||||
options: {
|
||||
config: {
|
||||
"my-fulfillment": {
|
||||
|
||||
@@ -78,7 +78,7 @@ module.exports = defineConfig({
|
||||
options: {
|
||||
providers: [
|
||||
{
|
||||
resolve: "./dist/modules/my-notification",
|
||||
resolve: "./modules/my-notification",
|
||||
options: {
|
||||
config: {
|
||||
"my-notification": {
|
||||
|
||||
Reference in New Issue
Block a user