Fix determining TSR version when running in certain configurations #1537
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
About the Contributor
Type of Contribution
This is a Bug fix / Code improvement for compatibility with later node versions
Current Behavior
Using
importwith a json file is banned in node 20 unless you usewith { type: 'json' }, which is not supported in node 16, our current build target.Question: Does using import freeze the value at sofie-core build time, not reflect the version that yarn has chosen to install? If so, is that the right thing to do?
New Behavior
Use require to import the
package.jsonfile.Testing
Affected areas
This PR affects building blueprints.
Time Frame
Status