#Using Aliases in backend?

14 messages · Page 1 of 1 (latest)

summer scarab
#

Looking at the demo, https://github.com/payloadcms/public-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 https://github.com/payloadcms/public-demo/blob/master/tsconfig.json
but getting error, has anyone been able to use aliases path?

Idealy importing like this

import MediaContent from '@/blocks/MediaContent';
#

I keep getting code: 'MODULE_NOT_FOUND',

summer scarab
summer scarab
#

@steep dock any ideas about this?

steep dock
#

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

summer scarab
#

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

summer scarab
#

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

tired crescent
#

I was able to get this working with module-alias 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.