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 am trying to migrate my CI/CD pipelines to use Bun but have an issue setting the configration for private repositories as I cannot programatically set them in the GH action like I can with npm ex: npm config set.
I believe there is an open issue for reading from .npmrc which would resolve this issue here, but I would also like the ability to set this directly in the bunfig.toml in a similar way (maybe bun config set install-scope '...'?)
What is the feature you are proposing to solve the problem?
Let users add configuration to bunfig.toml programatically -- bun config set [configOption] '...'
What alternatives have you considered?
I've tried to create a file by using cat, but with the specific structure of [option] ... [option2] ... it's not really possible lint the file. Having a way that does this automatically would be extremely helpful.
The text was updated successfully, but these errors were encountered:
What is the problem this feature would solve?
I am trying to migrate my CI/CD pipelines to use Bun but have an issue setting the configration for private repositories as I cannot programatically set them in the GH action like I can with npm ex:
npm config set
.I believe there is an open issue for reading from .npmrc which would resolve this issue here, but I would also like the ability to set this directly in the bunfig.toml in a similar way (maybe bun config set install-scope '...'?)
What is the feature you are proposing to solve the problem?
Let users add configuration to bunfig.toml programatically -- bun config set [configOption] '...'
What alternatives have you considered?
I've tried to create a file by using cat, but with the specific structure of [option] ... [option2] ... it's not really possible lint the file. Having a way that does this automatically would be extremely helpful.
The text was updated successfully, but these errors were encountered: