I've been going through the process of converting a project I'm working on into a monorepo using yarn workspaces, and I've been running into some issues with typescript files in my shared package when trying to compile my next.js web app:

Module parse failed: Unexpected token (3:5)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
| import styled from "@emotion/styled";
| 
> type Props = {

The weird thing is, we're using the swc compiler and not webpack, so I'm not sure why the webpack docs are being referenced here, and I'm not sure if this is a red herring and just outdated swc docs that were copy and pasted or if my project is actually trying to use webpack instead of swc now for some reason. If the latter, what might be causing this? We don't have any webpack.config.js any more and we do have a .swcrc

Some additional information: I have a path alias to the shared package set up in tsconfig.json, and I've also set up the references key in tsconfig.json of the web app to point to the shared package's directory. I've tried both with and without the shared package set as a dependency in package.json, and it doesn't seem to make any difference