<p dir="auto">There're some discussions about dependency management. I think when we people started to use deno to build complex programs, a dependency manager is desired. Removing node_modules from the project folder is a brilliant revolutionary design, but I'm not sure whether the package.json file also should be deprecated. Currently, people use a <code class="notranslate">deps.ts</code> file or <code class="notranslate">import_map.json</code> to manage the external modules, it seems like a central specification file is necessary, and module versioning is another important thing in production environment. In my opinion, manage these modules manually is definitely a terrible development experience, so I built this stuff <a href="https://github.com/denodep/dep">dep</a>, a simple cli to manage project dependencies, but unfortunately, I used a file called <code class="notranslate">pkg.json</code> (maybe will change to <code class="notranslate">spec.json</code>) to describe the information of the project, and a dependencies map like <code class="notranslate">package.json</code> do, the program will automatically generate or update a import map after adding external modules, so you can import any module with a relative URL. Also I kept all the features below:</p>
<ul dir="auto">
<li>keep no packages</li>
<li>keep ES modules semantics</li>
<li>keep file extension</li>
<li>keep remote URL imports (Source URLs in import map, relative URLs in scripts)</li>
</ul>
<p dir="auto">I just want to know if this is an acceptable solution? What are your opinions on this?</p>
<p dir="auto">Import from url is  very hard to use. I think is not a good idea.<br>
If so,</p>
<ol dir="auto">
<li>We must manage more js files not our own development.</li>
<li>Heavily dependent on the network, because the third package also can import another packages.</li>
</ol>
<p dir="auto">Like C#\Java, the nuget and maven is good for use. Maybe use that mode can help us manage the packages.</p>