Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handling development packages like languageserver #90

Open
telegott opened this issue Nov 13, 2023 · 2 comments
Open

Handling development packages like languageserver #90

telegott opened this issue Nov 13, 2023 · 2 comments
Labels
enhancement New feature or request

Comments

@telegott
Copy link

Hey!

First of all, thanks for this great effort. I'm just trying it out now, but it seems to fill a gap sorely needed, which was handled much better by other languages like Ruby (rbenv + bundler) or Python (pyenv + poetry) .
I haven't seen yet a functionality to separate out development packages like languageserver or test packages like testthat, which are relevant for CI, but should not be part of a deployed project. Is there an easy way to do this already, or, if not, is this a feature that is upcoming?

Best regards,
Michael

@b-rodrigues
Copy link
Contributor

Hi Michael,

thanks for your kind words and question!
As of now, this is not handled, but we could probably do something using nix develop I guess. We would need to explore this further. Thanks!

@philipp-baumann philipp-baumann added the enhancement New feature or request label Sep 20, 2024
@b-rodrigues
Copy link
Contributor

Ok so there is something to handle this now, but in specific case. If you use targets on CI, then using tar_nix_ga() places a script to run a targets pipeline on CI the root project's .github/workflows folder. This action contains a step to remove IDEs and the languageserver package:

- name: Prepare default.nix for CI

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants