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

Answer "how heavy is each of these deps?" #60

Open
tfiers opened this issue Jan 7, 2023 · 3 comments
Open

Answer "how heavy is each of these deps?" #60

tfiers opened this issue Jan 7, 2023 · 3 comments

Comments

@tfiers
Copy link
Owner

tfiers commented Jan 7, 2023

Indeed:

We won't install packages (ok if it is in active manifest, sure, we could).
But in general we won't (re #5)

So, a proxy? Size of src/ :) I like that

@tfiers
Copy link
Owner Author

tfiers commented Jan 7, 2023

Concrete motivation: I was weighing whether to add LiveServer to docs/Project.toml
(or alternatively to just have it in global v1.8 env)
and I see it introduced quite some new deps to Manifest

but ya know, they could all be tiny and fast so np

@tfiers
Copy link
Owner Author

tfiers commented Jan 7, 2023

I was weighing whether to add LiveServer to docs/Project.toml
(or alternatively to just have it in global v1.8 env)

(btw in the end I went with a secret, third solution: docs/localdev/Project.toml (see serve.jl))

@tfiers
Copy link
Owner Author

tfiers commented Jan 8, 2023

So concrete idea:

  • for installed in current project only
  • t0; eval using $module; t1
    Just go down list (or up list rather. 'topological sort')?
    And done. Add to graph nodes (maybe fade the lower ones. Or ooh flame 🔥 color scheme!)

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

No branches or pull requests

1 participant