Private servers

• http://cdn.bmc.com:4873
• http://172.25.144.178:4873
• http://10.19.48.11:4873/#browse/welcome

Good because:

• push your own packages
• cache common NPM packages
• have different version of the 3rd party package

package.json

dependencies -  are required in both development and prod

devDependencies -  are required in development

peerDependencies  -  allow you to state compatibility

Useful NPM commands

npm home (works for public)

npm repo (same)

npm ls

npm list package

npm outdated

npm pack

npm prune

npm link

npm audit

npm cache clean -f

npm completion >> ~/.bashrc

Everybody likes CSS

Bootstrap 4

Browsers support

When teams ask us to support IE7-8-9-10

...but customers are using it

Structure

Starting with a new framework

• Structure
• Dependencies
• Angular CLI
• Hello there
• Adapt demo repo
• Angular Package Format
• Polyfills and differential loading
• Server Side Rendering
• KLM experience

Versioning

• current versioning model 
• frequency of updates
• what changes expect in a short term
• what I need to know if I want to update to newer Angular

Communication

(we want you to speak up)

• github issues (preferable, all community benefits from it)

• slack (better than emails, good for quick questions)

• emails (don’t do that unless you are stuck on a desert island with email only)

Where should I look for info?

(docs, wiki, change log, source code for sure)

Can I change the docs? 

(spoiler - yes)

Staging servers

Testing