Absolute import paths via jsconfig.json compilerOptions.basePath not working in exposed modules?

[nickrobillard]

I am using jsconfig.json in order to use absolute import paths. In jsconfig.json, I have set compilerOptions baseUrl like this:

{
  "compilerOptions": {
    "baseUrl": "app"
  },
  ...

Then in a component, I am able to use absolute import paths, like this:

import SomeService from 'components/SomeService.js';

Relative to my package.json, SomeService.js path is ./app/components/SomeService.js. This works well outside of WMF. However, when using WMF and I expose this component, I see this error immediately:

ERROR in ./app/components/SomeService.js 24:0-67
Module not found: Error: Can't resolve 'components/SomeService.js' in '<path to parent component>'

Question
Is there a way for WMF to support my absolute import paths, or do I need to change them to be relative? Any insight is much appreciated!