Webpack log size problem about loader-webpack HOT 6 CLOSED

We're in the process of replacing the old 1.x Aurelia webpack plugin with a new 2.0 release currently in Release Candidate form.
If you're writing tutorials, you really don't want to be using 1.x anymore as 2.0 is a complete rewrite meant to be more flexible and easier to use. More importantly, 2.0 is not backward compatible with a 1.x configuration.

Given all the @easy-webpack stuff I'm tempted to think you're using 1.x plugins.

There's no docs in the hub for now, but some background information on 2.0 is in its wiki:
https://github.com/aurelia/webpack-plugin/wiki

New skeletons are available, just be aware that they don't reference the latest RC:
https://github.com/aurelia/skeleton-navigation/tree/master/skeleton-esnext-webpack

And some barebones, minimal examples can be found in my account:
https://github.com/jods4/aurelia-webpack-build/

from loader-webpack.

Thanks, @jods4 - more than great feedback. After discussing this situation pretty extensively (from the high level standpoint) with @EisenbergEffect, your more detailed comment will allow me to create the "alpha" versions of tutorial samples which target aurelia community developers using aurelia kendoui bridge plugin.

The current set of the tutorial samples are based on original skeletons ver 1.1.2, so I could appreciate your advice on how to proceed from this point onwards:

1. Rewrite the webpack targeting subset of my tutorial samples, using "your webpack" samples as the basis

2. Rewrite all of my tutorial samples using the current master as the basis.

Also, please be aware of my work on cli-based-skeletons which I initiated with the intent to help @JeroenVinke at the time he worked on cli last, and the now generally accepted idea to "teach" cli to be able to generate all today's skeleton was not generally accepted. Since Jeroen is on "college hiatus", it may be worthwhile to point out to this work - and I would certainly appreciate some feedback to that. The documents describing these skeletons exist here

from loader-webpack.

@adriatic My demos and the new skeletons should be similar when it comes to core Webpack features and both can be an inspiration. Just keep in mind that they don't have the same purpose or goal.

Skeletons are full featured setups that intent to include development config, production build, end-to-end testing and more. They have lots of dependencies on 3rd party libs and tie everything together in a large config. Obviously, they are opiniated and some choices were made that may not be everyone's.

My demos are minimal examples that demonstrate one specific aspect of the webpack plugin. They show how to get something working with as little code as possible and illustrate configuration for some specific use cases. I think they are a great "getting started" or learning tool, probably a little lightweight when it comes to building a large-scale app. None of them include automated tests for example. Only one of them has minification. And so on.

from loader-webpack.

Thanks, @jods4 - based on your explanation, what you have is perfectly fitting my needs. So, I will use is here and here, writing the same caveats you just stated yourself.

If you care to see what I will do with them, I will share my experience here

from loader-webpack.

I'm glad it helped.
Shall we close this issue then?

from loader-webpack.

It's really bad that GitHub does not create email notifications about added comments to any given thread 😞 . So, with apologies for being late, let's close this issue.

I would also like to share with you my success in using this new Webpack plugin in my Aurelia CLI Adventures which is my attempt to peek in the near future when Aurelia CLI will be able to generate all Navigation Skeletons from scratch (by describing the process of hand-assembling these skeletons).

from loader-webpack.