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.
What
Allow to override appPath and remoteCataloogRoot when writing symlinks with paths from env variables
Why
I have a very specific case where runtime exists in a different environment from development, so using this package I end up having symlinks that don't make sense for my system and IDE.
Locally I run meteor project dockerized with tilt. Outputs are reflected in my system because everything is mounted, but since process runs inside container zodern:types ends up generating symlinks that are resolvable only inside container.
So my solution is to manually provide paths for app and catalog root on host machine and pass them down in the container so that symlinks created by package are readable by host.
I didn't update anything in Readme regarding adding the variables since it's a very specific case and variables if misused can break functionality, so unless someone knows what they are doing they shouldn't touch that. But I can add it to readme if needed