How to master Deno config.links (equivalent npm link) ?
🧑💻JS / TS Development
Hello! 
I'm looking to improve my DX regarding Deno configuration links to override packages with local versions during development.
In terms of experience, using
When using Deno, the link information is stored in the
How do you use this feature on your end? I tried to:
Create a
Look for a flag during the CI build to not use the links, but I think such a flag doesn't exist.
Do you have any recommendations?
Thanks for your help and advices!
I'm looking to improve my DX regarding Deno configuration links to override packages with local versions during development.
In terms of experience, using
npm linknpm link is transparent. This means that this information only exists on my computer. Nothing will be committed to my repository when I'm using linked packages.When using Deno, the link information is stored in the
deno.jsondeno.json file (and in the lock one too). So I need to be careful when committing files to make sure I'm excluding the link property.How do you use this feature on your end? I tried to:
Create a deno.dev.jsondeno.dev.json as a special configuration during development. But without success because it requires maintaining both deno.jsondeno.json and deno.dev.jsondeno.dev.json. It seems like the configurations can't be merged ? Look for a flag during the CI build to not use the links, but I think such a flag doesn't exist.Do you have any recommendations?
Thanks for your help and advices!
