lintingto be able to opt-out of Typescript linting. Use
gulp serve --no-lintingfor faster builds.
@microsoft/teams-jspackage to version
watchgulp tasks now only rebuilds the parts that has changed (server side code, client side code, styles or static files) which improves incremental build times
gulpfile.jsto use the
$schemadefined in the manifest file for validation and the
SCHEMASobject only as backup
webpack.config.jsfile, and then the persisted config if exists, before defaulting to the library name
2.11.0-preview. It contains support for localization of your apps. You can either start a new project using the 2.11.0 version or you can update a project from 2.9.0+. The latter one I need help with testing on your existing projects, as it will do an update to
gulp.config.js- which is a new feature in the generator that allows us to update the core build files going forward, when new features are introduced. Test it on your existing projects - but ensure to have them under source control for any issues in this preview.
Is there a reason why all dependencies, even those not needed in production, are in
dependenciessection of package.json? IOW, any reason why
Very valid, that actually has an answer. The reason we did move everything to
dependencies is the fact that when you do a
git push to Azure and want to avoid having the compiled
dist included in Git, meaning Azure should do the build after the push. When Azure does the
npm install it did not pick up the
devDependencies so the build failed. I have not gone back and tested this for a long time and it was a know issue back then (if I recall with Kudu).
deploy.cmdnow and it uses
npm install --production(which causes only
dependenciesto be installed). If I remember I fiddled with that but did not get it to work, might be worth going back and test again #goodfirstissue :-)
npm install, it looks for an envvar that indicates if you are in PRODUCTION or not (which you can override by including the
--productionflag too. If not (like your laptop),
npm installpicks up everything in
devDependencies. But in An Azure WebApp has the envvar set to PRODUCTION so
npm installonly grabs what's in
/distor an equiv, what you currently have is your only option.
You say #goodfirstissue... would you be open to a PR that did two things: (1) moved what's needed =>
devDependencies & (2) modified the
deploy.cmd & docs to explain how to do a deployment that includes both if you use Azure web app capability of git deployment?
This would allow others who want a more enterprisey style deploy to use CI/CD to do the build NOT in production, but only deploy production assets (ie:
/dist) which would also keep
/dist out of the repo.