Not sure CorsConfig fields, or others, will accept regex and a list. I think they should if not.

[Davenporten]

I'm setting up some simple configuration for CORS on my graphql-mesh instance with something like

serve:
  cors:
    origin:
      - http://localhost:3000
        /http?:\/\/localhost(:\d+)?/

and it's failing (meaning I get a CORS error). If I have just the explicit url

    origin:
      - http://localhost:3000

it works fine, but if I have just the regex

    origin:
      - /http?:\/\/localhost(:\d+)?/

it fails. The type of origin is any (see here) which gave me the impression that you could basically pass whatever you want. I think at least a list should be allowable, but even if I have two explicit urls it fails. Does anyone have thoughts on this? Is there a way to at least get regex to be supported for the origin (that's really what I need the most)?

Thanks in advance for any thoughts.

[ardatan]

I think it is not supported by YAML syntax itself. Not sure how to solve it. Maybe a JS file can be used as a configuration file "mesh.config.js"

[Davenporten]

Gotcha, that's an interesting idea, I'll see what I can do and will report back here.

[Davenporten]

That did it! I converted .meshrc.yaml to .meshrc.js and put the following in

module.exports = {
    ...
    serve: {
	cors: {
            origin: [
                /https?:\/\/localhost(:\d+)?/,
            ]
         }
    },
    ...
}

You can of course put more items in the origin list.

As always thanks for all the help!