Skip to content
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

Document build process #514

Open
TimvdLippe opened this issue Sep 24, 2017 · 2 comments
Open

Document build process #514

TimvdLippe opened this issue Sep 24, 2017 · 2 comments

Comments

@TimvdLippe
Copy link
Member

This is a task for me. According to the messages in Slack, this build process remains a lot of magic. I should document the build to make it a lot clearer:

  1. Why does it exist?
  2. How does it work?
@TimvdLippe TimvdLippe self-assigned this Sep 24, 2017
@MatthijsKok
Copy link
Contributor

I would also like "Why did we choose this tool for this task (vs other tools) ?"

Some random questions I thought of to try to help you understand what needs clarification:

  • Why did we choose bower as our package manager?
  • Isn't yarn also a package manager?
  • Why do we apparently need both?
  • I've been hearing a lot about webpack lately, would that solve any of our problems?
  • Can't we just use the polymer CI toolset?

@TimvdLippe
Copy link
Member Author

RE: custom build. Over the past few months the polymer build command in the CLI has significantly improved and should now support most of the use-cases for which we initially had a custom build.

@TimvdLippe TimvdLippe removed their assignment Aug 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants