Collection hooks somehow affect the admin panel

mauz.

2 months ago

9

webpack: config => {
  config.externals = {
    sharp: 'commonjs sharp',
  }
  return config
},

const sharp = await import('sharp')

• 

  tylandavis

  Payload Team

  2 months ago

  hey @mauz. , there's a section in our docs about how we recommend aliasing server-only modules (like sharp). Have a look and let me know if this solves your issue.

  https://payloadcms.com/docs/admin/webpack#aliasing-server-only-modules
• 

  mauz.

  2 months ago

  Is there also an option for typescript? Because this right here still throws an error:

  
• 

  tylandavis

  Payload Team

  2 months ago

  looks like a typo, missing the

  s

  on

  mocks

  in your

  path.resolve
• 

  mauz.

  2 months ago

  Oh... my bad - now it works, but one error is still in the logs:

  
  

  cms:dev: Watchpack Error (initial scan): Error: ENOTDIR: not a directory, scandir '/app/apps/cms/src/hooks/imageGeneration.ts'

• 

  notchr

  2 months ago

  bad path?

• 

  mauz.

  2 months ago

  Don't think so - the path seems to match up with my structure.

  
• 

  .redjoker

  2 months ago

  @mauz. I needed the same thing today! I personally just looped my imageSizes and added a

  -webp

  variant using formatOptions.

  
• 

  mauz.

  2 months ago

  Huh that's interesting, thanks for letting me know!

  
  

  
  

  Tried it out - yep, works 100% better than my homegrown solution. I just don't get why features like this are buried in the docs.

  
  

  
  

  @tylandavis I think your docs need a few backlinks at relevant places or examples for common use-cases (like image-resizing).

  
  
  

  For example, I skimmed the entire REST api docs to find something that allows me to query items, instead of getting the whole collection, but never found anything (except for id, which wasn't helpful). So I created my own custom endpoint

  /bySlug/[slug]

  . Later I found out, from a forum post, that you have a query language/format for that. I guess now that I know what to look for it isn't particularly hard to find, but I expected to find all information about the REST api at the

  REST API

  menu point (or at the very least I expected there to be a paragraph which links to the Query docs).

• 

  tylandavis

  Payload Team

  2 months ago

  Thanks for the feedback @mauz. , we can definitely make some improvements to our docs regarding requests and queries.