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
pub build - expose other folders, not just web #14673
Comments
This comment was originally written by Erik.G...@gmail.com If I understand Sigmund's issue correctly, this would be useful for people making packages of polymer elements. For example, the polymer-elements library (https://github.com/Polymer/polymer-elements), is a collection of polymer elements with an entry point in example for each element. Also, what if I want to transform and run unit tests in javascript against the javascript version of the code? |
I'd love pub build to work with example/ and bin/ (for server-side apps, the build process is a bit different I presume, but creating a snapshot is a good first step) |
I don't think we're likely to want to use "pub build" with example folders or tests; those seem like a better fit with "pub serve", since they don't need to be deployed anywhere. That leaves "web" and "bin". Most apps aren't going to have both of these directories, so I don't really want to optimize the directory layout for all apps to handle the few apps that do. Maybe once we start supporting server-side building we can split up the subdirectories in that case in particular, though. |
This comment was originally written by @zoechi Actually I want to publish the examples of my libraries on i.e. Github pages so people can check them out without setting something up by themselves just to see if it contains what they are looking for (polymer elements). |
Removed Type-Defect label. |
Issue #11386 has been merged into this issue. |
This comment was originally written by ross.dart....@gmail.com I want to build the |
Marked this as blocking #13591. |
Removed Priority-Unassigned label. |
Marked this as blocking #15829. |
Set owner to @munificent. |
For reference, this is the current plan for this behavior: https://gist.github.com/munificent/8360674 |
Added Started label. |
Issue #16304 has been merged into this issue. |
Looks like the code was committed. Awesome! Added this to the 1.2 milestone. |
Added Fixed label. |
This comment was originally written by dev...@futureperfect.info great news! |
This issue has been moved to dart-lang/pub#695. |
pub build currently will create a 'build/' folder that contains whatever is under 'web/'.
I was wondering if we should make the 'web/' folder explicit, so we can later make room to add 'example/' and 'app/' as other folders generated under 'build/'.
The text was updated successfully, but these errors were encountered: