Is your feature request related to a problem? Please describe.
Currently, the project isn't set up to support absolute paths (i.e. src/pages/...). The project only supports relative paths (../../pages/...).
Describe the solution you'd like
To make it easier to manage and move files in the project, we would like to have the project support absolute paths and begin to migrate all our relative paths to start using absolute paths.
The best solution for this issue is just to reconfigure the project so that it has the ability to support absolute paths. There's no need to start migrating all relative paths since that can be addressed in a follow-up issue.
Describe alternatives you've considered
N/A
Additional context
It seems like our testing environment is the only reason why we don't support absolute paths. VSCode and TS are able to resolve paths as expected with absolute paths, but our Jest testing environment is unable to resolve modules.
Is your feature request related to a problem? Please describe. Currently, the project isn't set up to support absolute paths (i.e.
src/pages/...). The project only supports relative paths (../../pages/...).Describe the solution you'd like To make it easier to manage and move files in the project, we would like to have the project support absolute paths and begin to migrate all our relative paths to start using absolute paths.
The best solution for this issue is just to reconfigure the project so that it has the ability to support absolute paths. There's no need to start migrating all relative paths since that can be addressed in a follow-up issue.
Describe alternatives you've considered N/A
Additional context It seems like our testing environment is the only reason why we don't support absolute paths. VSCode and TS are able to resolve paths as expected with absolute paths, but our Jest testing environment is unable to resolve modules.