In @nextjs with @typescript, if you import outside your nextjs app folder (like in mono repos or mixing frameworks at code level instead "npming" components for whatever reason), you may receive an error due to the build process not recognizing ts files outside base paths.
e.g.: `import { member } from '../../lib/model/m1';`
Error message: "Module parse failed: You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file"
You can use an alias and `config . resolve . alias` in config.
Full sample at a code gist with a ref link to the author's solution (provided at @vercel/nextjs issues by @LincolnWDaniel at a different context but with similar solution).
💻Use of config.resolve.alias in NextJS config
gist.github.com/nilsandrey/ebcae24d844e76915e60047e5b63190b