Suggestion for new page in client side development

[damienbod]

Introduction to using Webpack in ASP.NET Core

I think this would be useful like the gulp, grunt pages.

[Rick-Anderson]

@danroth27 do we want this?
@damienbod would you be interested in writing this?
[@]SteveSandersonMS will review outline.

[damienbod]

yes, should I start?

[Rick-Anderson]

@damienbod Yes, Post the outline first.

[damienbod]

Document Outline:

• Introducing Webpack

• Preparing the application

  • Using Webpack with npm
  • Using Webpack with yarn

• Configuring Webpack

  • Production, Development builds, wwwroot
  • Modules Typescript
  • Modules SASS, LESS, CSS, HTML
  • Chunking
  • Hot Module Replacement
  • Plugins UglifyJsPlugin, CleanWebpackPlugin, HtmlWebpackPlugin, CopyWebpackPlugin

• Debugging with Webpack

[Rick-Anderson]

@SteveSandersonMS @danroth27 please review

[SteveSandersonMS]

Regarding this list of topics, do you think they could be phrased in terms of things that are unique to ASP.NET? As it stands, it sounds like general-purpose Webpack docs that could apply to any web application platform.

[damienbod]

@SteveSandersonMS
I did this, because this is how the gulp and grunt docs are written, which I think are done well. I decided to follow the same style. The contents will be ASP.NET Core or Visual Studio specific like the grunt/gulp docs.

Greetings Damien

[FabianGosebrink]

Hey, @damienbod and me just talked about that.

Maybe the document could fulfill the unique ASP.NET case in having the app in one folder inside Visual Studio (Code), building it into wwwroot, triggering it with a binding on starting or building the project and starting the production and development build out of Visual Studio.

Would that be worth a document?

Would love to help btw.

Fabian

[Rick-Anderson]

I did this, because this is how the gulp and grunt docs are written, which I think are done well.

Can't we just point to their well written docs? We should just be documenting what's unique to ASP.NET Core.

[damienbod]

@Rick-Anderson yes/no, I only want the documentate what you need to do inside Visual Studio to get Webpack working, or specific webpack configurations when working with an ASP.NET Core project, or publishing inside VS with ASP.NET Core or just using Webpack inside VS.

I was refering to the titles, which are as @SteveSandersonMS pointed out general. The titles are just subtitles. My suggestion for the title is "Introduction to using Webpack in ASP.NET Core" and the subtitles are the document outline.

Also I was thinking of documentating everything for Visual Studio, didn't think about Visual Studio Code.

?

[Rick-Anderson]

@damienbod It would be great to include VS Code.

[danroth27]

We do want to start moving the content around JavaScriptServices, which includes a bunch of webpack related functionality, but we should avoid trying to redocument webpack itself.

[danroth27]

We had some proposed outlines in #2461 that we should take into account.