Update module-path-aliases.md

[wiredacorn]

Bug

• Related issues linked using fixes #number
• Integration tests added
• Errors have a helpful link attached, see contributing.md

Feature

• Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR.
• Related issues linked using fixes #number
• e2e tests added
• Documentation added
• Telemetry added. In case of a feature if it's used or not.
• Errors have a helpful link attached, see contributing.md

Documentation / Examples

• [X ] Make sure the linting passes by running pnpm build && pnpm lint
• [X ] The "examples guidelines" are followed from our contributing doc

[ijjk]

Suggested change

	The additional `paths` are reletive to the `baseUrl`. For example:
	The additional `paths` are relative to the `baseUrl`. For example:

[ijjk]

I think this example may cause confusion as baseUrl shouldn't really be used in this way and more so should point to the packages base. Potentially it could show a nested package as the baseUrl and including shared utils in paths?

[wiredacorn]

Oh ohk. I am pretty new to NextJS, so I was not aware this is a bad practice. It does seem to be working in my project, but I think we could just remove this example.

I do think that it would still be helpful to mention that the paths will start at the baseUrl location instead of the root.

[ijjk]

Yeah sounds good to keep just the note and maybe strip the example 👍

[wiredacorn]

Ok, I have removed the example and also added a commit with a better example in case you want to include one.

[styfle]

Suggested change

	Each of the `"paths"` are reletive to the `baseUrl` location. For example:
	Each of the `"paths"` are relative to the `baseUrl` location. For example: