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.
@jsuddsjr , @cagdasdavulcu - I have not made out any detailed plans yet, a lot of things depends on what features Microsoft is releasing and when (they do have some nice stuff coming that will make sense to add)
What's on my list currently is
--importfeature, that creates a project from a Teams app package created from the App Studio
Would you be interested in setting up a Teams call on this after the holidays?
@wictorwilen RE sync in early JAN - LGTM... I'd personally love to tweak the project structure, but not sure if I'm the only one who struggles with the current setup. I'm also relatively new to using it so very well may just be me, but I think it can be simplified & make it more clear what's client vs. what's server.
Also... i've got the startdust stuff implemented with theme switching in tabs. If you like how it's setup in these MS Learn modules I've done, I can take that feature on... https://github.com/OfficeDev/TrainingContent/blob/master/Teams/30%20Create%20Embedded%20Web%20Experiences%20with%20Tabs%20for%20Microsoft%20Teams/Demos/01-learn-msteams-tabs/src/app/scripts/learnPersonalTab/LearnPersonalTab.tsx