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.

Sign up for GitHub

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

Jump to bottom

suggestion: centalise external dev dependencies #3795

Closed
iuioiua opened this issue Nov 12, 2023 · 2 comments · Fixed by #3821
Closed

suggestion: centalise external dev dependencies #3795

iuioiua opened this issue Nov 12, 2023 · 2 comments · Fixed by #3821
Labels
good first issue Good for newcomers

Comments

@iuioiua
Copy link
Collaborator

iuioiua commented Nov 12, 2023 •
edited

Having a dev_deps.ts or similar somewhere containing all the external development dependencies is a good idea. It'd allow us to manage/update these dependencies, even do it automatically. External dependencies will have to be audited to determine which approach is best.
@iuioiua iuioiua mentioned this issue Nov 12, 2023
Merged
@lino-levan
Copy link
Contributor

I think it would be best to just put them in the deno.jsonc? No need for a deps.ts file I think.

@iuioiua
Copy link
Collaborator Author

iuioiua commented Nov 13, 2023

Yep! That'd be better actually.

@iuioiua iuioiua added the good first issue Good for newcomers label Nov 14, 2023
This was referenced Nov 15, 2023
Closed
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue Good for newcomers
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

chore: centralise dev dependencies in deno.json denoland/deno_std
2 participants
@lino-levan @iuioiua