Webpack,asp.net核心,docker：使用dotnet调试或发布版本构建webp

>构建,部署等通过npm脚本处理
>每当有人检查分支,提交提交或添加新的供应商依赖关系时,他们运行npm run build-webpack-dev-vendor,这是一个运行npm-run webpack的npm脚本–env.dev –config ./配置/ webpack.config.vendor.js
> Docker构建也是从npm脚本运行的

来自webpack的构建输出被放入wwwroot目录,其整个内容被gitignored(除了.gitignore).

Webpack脚本

这些脚本用于任何或所有webpack构建.

"build-webpack-dev": "npm run build-webpack-dev-vendor && npm run build-webpack-dev-app","build-webpack-dev-vendor": "npm-run webpack --config ./config/webpack.config.vendor.js --env.dev","build-webpack-dev-app": "npm-run webpack --env.dev --display-modules","build-webpack-prod": "npm run build-webpack-prod-vendor && npm run build-webpack-prod-app","build-webpack-prod-vendor": "npm-run webpack --config ./config/webpack.config.vendor.js --env.prod","build-webpack-prod-app": "npm-run webpack --env.prod --display-modules",

我们的配置无法识别prod和dev供应商构建.
注意：需要安装npm-run.

Docker脚本

这些脚本用于构建和发布我们的docker镜像.
我们有快速的脚本变体,可以加快发布速度(无需重建,无需额外登录).

"docker-build-prod": "dotnet publish --configuration Release && docker build binReleasenetcoreapp1.1publish -t company/product:tag --no-cache","docker-publish-prod": "npm run docker-build-prod && docker login && docker push company/product:tag","docker-publish-prod-fast": "docker push company/product:tag","docker-login": "docker login",

如果应用程序中有任何捆绑包应该移动到供应商捆绑包(因此在webpack构建中使用–display-modules),开发人员应检查构建输出.

补充脚本

最后,并非我们团队中的每个人都使用Visual Studio(例如设计师).我们为它们提供了脚本和一些更通用的脚本.
快速变体跳过npm install,构建供应商包并恢复nuget包.

"start-dev": "npm install && npm run build-webpack-dev && dotnet restore && dotnet run --configuration Debug --environment "Development"","start-dev-fast": "dotnet run --configuration Debug --environment "Development"","start-prod": "npm install && npm run build-webpack-prod && dotnet restore && dotnet run --configuration Release --environment "Production"","start-prod-fast": "npm run build-webpack-prod-app && dotnet run --configuration Release --environment "Production"",

最后,好的措施

"refresh": "npm install && dotnet restore"

我希望有帮助,我愿意就如何改进这个问题提出建议:)