Skip to content

pub package manager support for new project template #2432

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

Closed
DartBot opened this issue Apr 3, 2012 · 19 comments
Closed

pub package manager support for new project template #2432

DartBot opened this issue Apr 3, 2012 · 19 comments
Assignees
Labels
closed-not-planned Closed as we don't intend to take action on the reported issue type-enhancement A request for a change that isn't a bug

Comments

@DartBot
Copy link

DartBot commented Apr 3, 2012

This issue was originally filed by [email protected]


Per the discussion of the Dart package manager, I'm requesting an additional "pub" command to create a new project with a standard layout and files.

Use:

pub new awesome_app

This will create a folder named "awesome_app" with:

  • a package description/dependencies file (correctly configured, so if a package needs to declare its own version in addition to declaring its dependencies, this is already filled-in);
  • a packages directory;
  • an awesome_app.dart program, or whatever;
  • etc.

Extensions:

Maybe supports "client", "server", "both" sub-commands so that these project types can be autogenerated appropriately (including io or html or json libraries, etc).

@munificent
Copy link
Member

Removed Type-Defect label.
Added Type-Enhancement label.

@DartBot
Copy link
Author

DartBot commented Apr 4, 2012

This comment was originally written by @chrisbu


Similar to issue #2435, it would be great if the functionality described above was available to apps by being able to #import pub itself and call functions on pub directly.

 (Ok, as a workaround, you could just start pub as a process from another dart script).

@kasperl
Copy link

kasperl commented Apr 11, 2012

Added Area-Pub, Triaged labels.

@DartBot
Copy link
Author

DartBot commented May 1, 2012

This comment was originally written by @butlermatt


This discussion is turning interesting. The package manager seems to be converting to a general purpose framework controller, similar to Rails, Padrino, etc. So as oppose to just a 'gems' functionality, we're creating projects, running a development web server, deploying/finalizing scripts and compiling/minifying. Would this functionality then become integrated with the Dart editor (either adding new functionality or replacing the current existing functionality). I'm certainly not against this direction, however if it is the direction you'll be taking then you may want to consider other features they provide as well from the get go (MVC generation, console servers, etc) rather than seeming like you're just tacking on cool features. Already with serve and deploy commands it seems to be becoming more than just a package manager (at least of the ones I've used, gems and cpan), and more of an all encompassing project manager which, as a subset, also handles/manages the packages of a project. Again, I'm not against the idea, just think that if it's the direction you're going it should be considered that from the beginning and designed as such.

@munificent
Copy link
Member

Added this to the Later milestone.

@munificent
Copy link
Member

Issue #7181 has been merged into this issue.

@pq
Copy link
Member

pq commented Jan 11, 2013

FWIW: I'm in the process of porting the editor's project template creation to dart (dartbug.com/7856) with an eye towards providing a simple stand-alone commandline tool for quick and easy project bootstrap. If that would meet your needs, feel free to merge this request into that one. In the long run, I'd love to see this tool (and possibly pub too) behind some kind of framework controller (a la the go command --- http://golang.org/doc/articles/go_command.html).

@munificent
Copy link
Member

Set owner to @pq.

@DartBot
Copy link
Author

DartBot commented Apr 3, 2013

This comment was originally written by [email protected]


At today's hackathon a team struggled because they put their unit tests under the "tests" directory instead of the pub required "test" directory. They wasted a lot of time confused by an import error. Perhaps if pub auto-populated the directory structure this could have been avoided.

@DartBot
Copy link
Author

DartBot commented May 14, 2013

This comment was originally written by [email protected]


I think it could work like leiningen for clojure (https://github.com/technomancy/leiningen).

@DartBot
Copy link
Author

DartBot commented Mar 24, 2014

This comment was originally written by [email protected]


All I want from this is to generate a bare-bones pubspec.yaml, kind of like npm init in node.js.

I basically want just enough that "pub install" works with all available fields provided.

@kasperl
Copy link

kasperl commented Jul 10, 2014

Removed this from the Later milestone.
Added Oldschool-Milestone-Later label.

@kasperl
Copy link

kasperl commented Aug 4, 2014

Removed Oldschool-Milestone-Later label.

@nex3
Copy link
Member

nex3 commented Aug 27, 2014

Issue #20701 has been merged into this issue.

@sethladd
Copy link
Contributor

We'll encourage the community and tools to deliver this.


Added NotPlanned label.

@nex3
Copy link
Member

nex3 commented Aug 27, 2014

Issue #20701 has been merged into this issue.

@nex3
Copy link
Member

nex3 commented Sep 19, 2014

Issue #20997 has been merged into this issue.

@DartBot DartBot added Type-Enhancement closed-not-planned Closed as we don't intend to take action on the reported issue labels Sep 19, 2014
@nex3 nex3 mentioned this issue Jun 3, 2015
@DartBot
Copy link
Author

DartBot commented Jun 5, 2015

This issue has been moved to dart-lang/pub#34.

@kevmoo kevmoo added type-enhancement A request for a change that isn't a bug and removed type-enhancement labels Mar 1, 2016
@Zectbumo
Copy link

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-not-planned Closed as we don't intend to take action on the reported issue type-enhancement A request for a change that isn't a bug
Projects
None yet
Development

No branches or pull requests

8 participants