You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
import'../src/components/appBootstrap/MultiversalGlobalExternalStyles';// Import the same 3rd party libraries global styles as the pages/_app.tsx (for UI consistency)
import'@/app/components/MultiversalGlobalExternalStyles';// Import the same 3rd party libraries global styles as the pages/_app.tsx (for UI consistency)
[Cypress releases "Real World App" (RWA) - Blog post](https://www.cypress.io/blog/2020/06/11/introducing-the-cypress-real-world-app/)
54
+
55
+
## Module path alias mapping
56
+
57
+
We use module alias path mappings, to avoid using relative paths (e.g: `../../src/common`) but absolute paths (AKA "module paths") instead (e.g: `@/common`).
58
+
59
+
Although it's simpler to use, it's harder to configure because it affects several configuration files:
60
+
- The paths mapping in `tsconfig.json:compilerOptions.paths` must match those in `../tsconfig.json:compilerOptions.paths`
61
+
- They must also match those in `jsconfig.json` file, which is necessary for WebStorm to understand them for .js files.
62
+
63
+
If the module path mappings aren't properly set everywhere, it won't work.
64
+
65
+
> You can still use relative paths.
66
+
67
+
Reference:
68
+
- See [Next.js "Module path aliases" documentation](https://nextjs.org/docs/advanced-features/module-path-aliases)
69
+
- See [WebStorm issue](https://intellij-support.jetbrains.com/hc/en-us/community/posts/360003361399/comments/360002636080)
0 commit comments