This is still WIP but opening now to be able to coordinate with @IgorMinar and @yjbanov

@IgorMinar and @yjbanov - I would like to discuss how to organize folders so both JS and Dart versions are "close" to each other but without stepping on each other toes

Remaining tasks:

• co-exist / unify with Dart
• run e2e tests before reporting numbers (only report numbers when tests are passing)
• make sure that we can have multiple tests (hello world, TodoMVC etc.)

We are already measuring the size of "hello world" app under modules/playground. Do we want to switch to a different app?

As for directories, for Dart it would be straight-forward to reuse the modules_dart directory, which is already friends with gulp. What do you think?

We are already measuring the size of "hello world" app under modules/playground. Do we want to switch to a different app?

Yes, this is what I got from the discussion with @IgorMinar in https://docs.google.com/document/d/14_PBtkOL0vyyRFmXxkRnz6GFWXjYisxZohDxdl1jV4c/edit#
Indeed setup for a WebPack-based app will be different as compared to a generic playground one.

As for directories, for Dart it would be straight-forward to reuse the modules_dart directory, which is already friends with gulp. What do you think?

Yup, I saw your work on the Dart tracking, but my understanding was that @IgorMinar wants to unify somehow both TS and Dart (as much as it makes sense, of course)

Sounds good. Looks like you have some vision behind this. I'd like to play an implementor role in this effort, so tell me what I should do :) Otherwise, I can just plug a todo app into what we currently use to measure Dart code size.

The rest looks good

@IgorMinar I've addressed most of your comments and going tackle the remaining one (removing calls to q.denodify) in a separate PR. Do you want to have another look at this PR or is it good to go?

Merging PR #6434 on behalf of @rkirov to branch presubmit-rkirov-pr-6434.

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}