Hacker News new | ask | show | jobs
by ARussell 1891 days ago
You could opt to improve upon the standard practice, right? I have only played with Demo a little, but the deps file seems only like a convention rather than a strict rule.

Why not instead create a deps directory, and keep in it one file per dependency? Inside each file, you re-export the library from URL.

This way you can import from files rather than URLs elsewhere in your code, and it should be clear which dependency is being imported from the file name itself.

1 comments

That solution is great! But it sounds like something that could be automated or managed for me.