Skip to content

Some common NPM MSBuild targets and other utilities used in ASP.NET (Core) MVC and Orchard (Core) CMS development.

License

Notifications You must be signed in to change notification settings

CityofSantaMonica/NPM-Targets

 
 

Repository files navigation

Lombiq NPM MSBuild Targets

Lombiq.Npm.Targets NuGet

About

Provides automatic NPM package installation and a custom NPM command execution before building a .NET project. This way it is possible for example to manage assets (e.g. .scss files or images) in a folder that will be automatically compiled into the wwwroot folder on build, which then can be excluded from the version control system.

Note, that these operations are optimized by running them only if the corresponding files have been changed.

Also see our Gulp Extensions library that contains some useful Gulp helpers.

Do you want to quickly try out this project and see it in action? Check it out in our Open-Source Orchard Core Extensions full Orchard Core solution and also see our other useful Orchard Core-related open-source projects!

How to use

Install the NuGet package or if you use the project from a submodule, add the following lines to the csproj file where the package.json file is. Make sure that the paths are pointing to the Lombiq.Npm.Targets.props and Lombiq.Npm.Targets.targets files of this project.

<Import Project="path\to\Lombiq.Npm.Targets\Lombiq.Npm.Targets.props" />
<Import Project="path\to\Lombiq.Npm.Targets\Lombiq.Npm.Targets.targets" />

The npm install (or pnpm install, see below) command will be executed but only if the package.json file exists and has been changed since the last build (i.e. you un/installed packages or up/downgraded ones). Note that if you update NPM then the package.json and package-lock.json files can change on npm install; currently, there's no way to prevent this (npm ci is much slower).

An npm run dotnet-prebuild --if-present script will be also executed during the build process which can be utilized to run a Gulp task for example. This will only happen if the files defined in NpmDotnetPrebuildWatchedFiles have changed (to achieve incremental build).

If you want to utilize this then add a dotnet-prebuild script to the package.json file like this (gulp build is just an example of a command you can run; you can also run the default gulp command with just gulp):

{
  "private": true,
  "scripts": {
    "dotnet-prebuild": "gulp build"
  }
}

Similarly, you can execute npm run dotnet-postclean --if-present via the dotnet-postclean script to clean up anything after an MSBuild Clean, for example:

"scripts": {
  "dotnet-postclean": "gulp clean"
}

Using pnpm for package restore

Pnpm is a faster and more efficient package manager. If it's installed globally, then the module will use that instead of npm to restore packages.

To install pnpm globally run this command: npm install pnpm -g. Once it's complete, the module will automatically use that to restore packages.

Contributing and support

Bug reports, feature requests, comments, questions, code contributions, and love letters are warmly welcome, please do so via GitHub issues and pull requests. Please adhere to our open-source guidelines while doing so.

This project is developed by Lombiq Technologies. Commercial-grade support is available through Lombiq.

About

Some common NPM MSBuild targets and other utilities used in ASP.NET (Core) MVC and Orchard (Core) CMS development.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published