Static build

[kotyara85]

Hey there,
So I'm building graphql mesh with a build command, I do use vars and those are written into index.ts (aka hardcoded)
Is there a way with a static build override those during the mesh start up?
Thanks!

[ardatan]

How do you use variables? If you use dynamic variables, they shouldn't be written in the artifacts.
https://the-guild.dev/graphql/mesh/docs/guides/dynamic-vars#env-variables

[kotyara85]

btw I use reflections for grpc - #5442

Weirdly enough I can only upgrade to 0.89.7

{
  "name": "graphql",
  "version": "1.0.0",
  "main": "index.js",
  "license": "MIT",
  "dependencies": {
    "@graphql-mesh/cli": "^0.89.7",
    "@graphql-mesh/graphql": "^0.96.5",
    "@graphql-mesh/grpc": "^0.29.19",
    "@graphql-mesh/openapi": "^0.98.1",
    "@graphql-mesh/plugin-prometheus": "^0.96.6",
    "@graphql-mesh/runtime": "0.97.6",
    "@graphql-mesh/transform-filter-schema": "^0.96.5",
    "@graphql-mesh/transform-naming-convention": "^0.96.5",
    "@graphql-mesh/transform-rename": "^0.96.6",
    "@graphql-mesh/transform-replace-field": "^0.96.5",
    "apollo-server": "3.13.0",
    "graphql": "^16.8.1",
    "prom-client": "^15.1.0"
  }
}

[kotyara85]

Ok, upgrading to grpc to ^0.98.5 fixed the issue. Thanks!

[kotyara85]

But all grpc services are erroring out with Failed to generate the schema TypeError: Invalid value used as weak map key now
sigh

[ardatan]

Like I said earlier, I need a reproduction in order to help you :)

[kotyara85]

Totally understand, That would be difficult as that happens on some of our grpc services only, I think this's the issue opened - #6424

The only version which doesn't return any errors is 0.29.19, but that version is not working with env vars
Anyway, closing this one as it looks like there's no solution at this point.
Thanks