You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 22, 2024. It is now read-only.
Angular 2 now is able to run on the server so what's the next step?
We can now take advantage of the benefits of having this control over the client's environment. We can create a small server layer that uses any of the underlying Node Frameworks such as ExpressJS, Hapi.js, or Koa.js. Doing so would be a great way for, normally client only developers, to be introduced to the backend.
Having full control over the client's environment allows us to dramatically improve the developer experience with features such as:
TypeScript inline script tags
ES6 features such as and SystemJS
allow users to write a component DSL (such as JSX, RiotJS, or jsBlocks)
better control over testing/development/production environments
better logging
live app configuration
default jwt setup
asset pipeline
inject ES6 polyfills
inject RxJS as Observable
can be front-end agnostic
removing unnecessary Angular imports for each file (like Rails)