feat: v5 no-config

[johnjenkins]

What is the current behavior?

• When there is no tsconfig - error
• When there is no stencil.config - use www as the default output. Global style / script not supported
• namespace defaults to 'app' (and throws a warning)
• During dev, when there is no index.html there's nothing to serve

GitHub Issue Number: N/A

What is the new behavior?

• When there is no tsconfig - a sensible modern one is auto-written
• When there is no stencil.config - use loader-bundle as the default output. Global style / script are supported by convention (src/global.css | scss | less | etc / src/global.ts | js)
• namespace is derived from package.json name
• During dev, when there is no index.html, auto-generate a dev-preview in every directory that a component lives.
  1. Uses an auto-loader to bootstrap components
  2. Auto loads global styles if present
  3. Uses an empty component <tag> as fallback, but uses CMP-DIR/usage/*.md (nested tagged html examples) for explicit, configurable demos

Documentation

Does this introduce a breaking change?

• Yes
• No

Anyone currently relying on www being the default will need to add a stencil.config with a www output

Testing

Other information