Using Aliases in backend?

default discord avatar
9 months ago

Looking at the demo,

I see a lot of imports like this

import MediaContent from '../../blocks/MediaContent';
import populateFullTitle from './hooks/populateFullTitle';
import MediaSlider from '../../blocks/MediaSlider';

I tried to use aliases by modifying the tsconfig file

but getting error, has anyone been able to use aliases path?

Idealy importing like this

import MediaContent from '@/blocks/MediaContent';

I keep getting


I see this structure was used on the website,

but not sure why the same thing doesnt working for the cms

@jmikrut any ideas about this?

  • discord user avatar
    Payload Team
    9 months ago

    Yes, I am about to step out for a bit but this has been covered a few times before in GitHub discussions. You have to alias in a few places (TS, Webpack, and Node itself) for the CMS

    here's one

    but this one i don't think was ever solved fully. but it will give you some background

    i know people do it

  • default discord avatar
    9 months ago

    oh I see

    yeah this is exactly my issue right now, VSCode recognizes the path but running dev server gives error that module not found

    I gave up on this after spending 3 hours, I could not get it to work, I think it would be great if this can be done easily like nextjs so just modifying the tsconfig file could work

  • default discord avatar
    4 months ago

    I was able to get this working with


    package and have the typescript intellisense working. I'm going to attach a few screenshots for reference if anyone else comes across this. If anyone has suggestions on doing this natively with node instead of using that package I would love to hear it.

Open the post
Continue the discussion in Discord
Like what we're doing?
Star us on GitHub!


Connect with the Payload Community on Discord



Can't find what you're looking for?

Get help straight from the Payload team with an Enterprise License.