frontend-packagers
                                
                                 frontend-packagers copied to clipboard
                                
                                    frontend-packagers copied to clipboard
                            
                            
                            
                        clearify #responsibilities and some other things
Great Comparison, thanks :+1:
I have some questions and ideas:
https://github.com/wilmoore/frontend-packagers#responsibilities It's not clear to me what the meaning of these things are:
- ~~package management~~
- ~~project bootstrapping~~
- project scaffolding
- build automation
- script/module loading
- ~~compile/build~~
- what is the difference between 2 and 3?
- what does 4 means? a build tool with a watcher?
- what is 5? component has a built-in module loader, or what does it mean?
https://github.com/wilmoore/frontend-packagers#development-dependencies I would like to add some features of component with a PR. In component you can even add local JS and CSS files for test environment, here is an example
https://github.com/wilmoore/frontend-packagers#package-contents component even works if a module brings it's own require. For instance mocha doing this and it works in component. Maybe mocha can be used as a test, to verify if it's possible ^^
https://github.com/wilmoore/frontend-packagers#package-contents What you think about to add fonts and images and especially URL rewriting in CSS files?
what is the difference between 2 and 3?
- bootstrapping is the ability to generate a fully working application (i.e. hello world, simple blog, etc.) from a template.
- scaffolding is the ability to generate parts of an application (i.e. model, controller, view, migration) from a template.
Probably should update the description with the above. Would you like to submit this as a PR?
what does 4 means? a build tool with a watcher?
Well, some build tools do not come with a watcher; however, yes, this is correct.
what is 5? component has a built-in module loader, or what does it mean?
script/module loading refers to when a tools includes it's own method of loading scripts. For example, some tools, when bundling your app, will provide a require function.
I would like to add some features of component with a PR.
Sure. Sounds fine to me.
What you think about to add fonts and images and especially URL rewriting in CSS files?
PR would be great.
Probably should update the description with the above. Would you like to submit this as a PR?
yes sure :)
script/module loading refers to when a tools includes it's own method of loading scripts. For example, some tools, when bundling your app, will provide a require function.
But then I don't understand why there is no checkbox for component and browserify (volo I don't know). Both provide the CommonJS require() and this fact is also written down at: Supported JavaScript Module formats. Shouldn't these points correlate?
But then I don't understand why there is no checkbox for component and browserify.
I'm not really sure why I checkboxes for component and browserify were not added initially (hard to recall the reasons from that long ago), but at this point, yes, I agree they should be added.