You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to add .NET binding to Projen, which works, but as I do JSII changes as well, I'd like to use my local JSII for it. When executing JSII_RUNTIME=<jsii dir>/packages/jsii-runtime/bin/jsii-runtime yarn compile in projen dir, it is using the version from node_modules.
I did not find pointers to it either here or in projen or I'm doing something wrong.
What is the expected workflow when one debugs JSII bugs comping up with other packages development cycle?
UPDATE:
I think that the problem is that the JS runtime does not support the JSII_RUNTIME variable and will always use the bundled version. Am I right?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm trying to add .NET binding to Projen, which works, but as I do JSII changes as well, I'd like to use my local JSII for it. When executing
JSII_RUNTIME=<jsii dir>/packages/jsii-runtime/bin/jsii-runtime yarn compile
in projen dir, it is using the version fromnode_modules
.I did not find pointers to it either here or in projen or I'm doing something wrong.
What is the expected workflow when one debugs JSII bugs comping up with other packages development cycle?
UPDATE:
I think that the problem is that the JS runtime does not support the
JSII_RUNTIME
variable and will always use the bundled version. Am I right?Beta Was this translation helpful? Give feedback.
All reactions