Using Aliases in backend?

generator1012 years ago

4

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

import MediaContent from '@/blocks/MediaContent';

• 

  jmikrut

  2 years 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

  
  

  
  

  https://github.com/payloadcms/payload/discussions/505
  

  
  

  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

• 

  generator1012 years 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

• 

  reepicheep05last year

  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.

  
  

  
  

  

  

  
• 

  twansparantlast year

  Hi @reepicheep05 I'm trying to achieve the exact same thing as you. My typescript paths are working in my editor, but I'm still getting the

  Cannot find module '@collections/Pages'

  error on start. I'm trying to setup these module-alias, but I was wundering if you also added this line somewhere like stated in the docs:

  https://github.com/ilearnio/module-alias#usage
  
  

  Then add this line at the very main file of your app, before any code
  require('module-alias/register')