Import Statements At Root

[alexfinnarn]

It is a huge PITA to use relative imports. You can add root imports with the @ symbol, but it takes some setup.

References:

• https://nextjs.org/docs/advanced-features/customizing-babel-config
• https://whoisryosuke.com/blog/2018/nextjs-tip-relative-es6-modules/

Required

What area of the codebase does this involve?

This touches everything.

Acceptance Criteria

• [ ] Devs can use root imports
• [ ] a .babelrc file exists in the repo

or

• [x] .babelrc file, 'import/resolver': 'babel-plugin-root-import' in eslint config, and dependencies babel-eslint babel-plugin-root-import eslint-import-resolver-babel-plugin-root-import eslint-plugin-import are all deleted from the codebase

[alexfinnarn]

Changing all imports actually is a PITA too. If you're importing code from the same directory, and that will likely not change, then why add directory prefixes to that import statement? So, I left a few relative imports.

[alexfinnarn]

This did not work with yarn build and I'm not sure how it worked with yarn dev. I think TypeScript complicates the root import, but there are like four config files involved in the whole mess now...and a few dependencies that can be removed if root imports are too much of a PITA to quickly implement.