aspnet-webpack support? about javascriptservices HOT 2 CLOSED

It only means that its intended usage is within those templates only. It doesn't mean that you shouldn't use it at all, but rather that its design is entirely to support those templates, and we're not implementing any features for other scenarios outside those templates.

from javascriptservices.

Thanks Steve for your quick response. I appreciate all your efforts and these templates are a huge time-saver for people like me to get started on a new project. The downside is, the day after I download your template, it becomes "My Critical Web App". It grows, changes, and evolves, and continues to have a direct reference to that unsupported library. The references to Node, for example, are supported by the community, not just for that template usage, but for general use, including production apps. That's not the case with the aspnet-webpack library. For us that lib is a black box that we don't understand and therefore can't extend on our own. I totally get why it's not feasible for you to launch a huge effort to support wider usage 'in the wild'. I guess the bottom line is I would caution anyone about to use this template that it is built upon at least one dependency that is not intended to be used beyond the initial template/proof of concept phase. Any future evolution of that code and you're on your own (for example, webpack 4 support).

Thanks again,
Randy

from javascriptservices.