Using the MicrosoftAspNetCore.ClientAssets packageĪll of this build logic can be included in a NuGet package and reused across multiple projects. For example, we only want to run npm install when the packages are not available locally or when the package.json file has been updated. Ideally, we want these steps to be incremental, meaning that they only run when any of the inputs have changed and don’t run when everything is up to date. NET and doesn’t require any additional setup. This is more inline with how builds work in. gitignore file to avoid accidentally adding the outputs to source control, and it makes cleaning the workspace harder. However, if you’re using Git (or some other version control system), you may be forced to add an entry into the. This is common in many tools and makes it easy to glance at the output. Put the outputs in the dist subfolder.
In our examples, we’ll put all the client web asset sources into an assets folder within the root of the project.įor the output of the build process we have a couple of options: Build/generate client web assets and include the results as part of the build output as static web assets.Restore client web assets managed by other package managers (npm, yarn).There are two things that we want to happen as part of the build process to integrate handling of client web assets: While the focus of this post is npm and webpack, the solution that we provide here can easily be adapted to other tools like yarn, rollup, etc. We’ll also walk through all the details of how to set this up using MSBuild for folks that want to be able to control and customize the process. For folks who want a solution that just works, we’ll look at the new experimental package that handles this integration for you automatically provided you have the right tools installed. In this post we’ll show you how to integrate npm and webpack into the build process for your Razor Class Library. It’s error prone and sometimes results in fragile solutions, like relying on the ordering of tasks in the build process that can change between releases. But integrating a client web asset build pipeline into the build process of a Razor Class Library can be challenging. Client web assets often need to be built or processed using tools like npm and webpack. NET class libraries setup with the Razor SDK to enable building Razor files (.razor, cshtml) and to include client web assets (.js.
0 kommentar(er)
