set this to use relative paths for component assets.

When it fails silents, usually it’s related to the DOM, here I list some cases I’ve come over.

• Pay close attention to inputs/outputs spelling

An npm module preferred. Most web resources are outdated.

It’s tempting to have tabs install from a local directory. But there are some issues associated. Suggestion timoxley/linklocal.

• Be aware of Update of local dependencies does not work

  This issue has been around for quite a while.

• npm link is ok, but it doesn’t look up your package.json file.

  which timoxley/linklocal addresses well.

tsconfig.json is always needed. Refer to ng2-heroes for a sample.

In package.json, there is the typings field to set. Refer to Typings for npm packages · Microsoft/TypeScript Wiki for details.

• Avoid opening a new browser window

  There is an ongoing issue about exposing browser-sync’s configuration objects in command line.

  For now, add open: false to sync.init in lite-server.js.

lite-server doesn’t really have any fancy features, use our own! browser-sync looks quite interesting though (so we don’t need our custom SSE).