* Fix usage of arrow functions as components
This fixes the React and Preact component as arrow function use-case by checking for the prototype property (arrow functions don't)
* Check the prototype
* Improved JSX framework detection
This improves the JSX detection and adds a bunch of test. The following is improved:
* If an error throws because of a coding mistake, those errors will be reported.
* We properly detect class components for both Preact and React. We don't have to "try to render" these.
It's still possible that error messages might be obscured in this scenario:
A Preact function component that uses hooks (or another preact specific feature) that has a coding mistake. The React renderer might throw when it uses the Preact hook. That error will be reported rather than the real coding mistake.
This is because we can't distinguish between errors that are due to the wrong framework and errors that the user caused.
I might reach out to the Preact community and see if they can think of a better solution to this problem. This will come up when other JSX based frameworks have renderers. I still think that having multiple frameworks in the same project is a feature worth trying to preserve.
* Move try/catch into the __astro_component
* Prevent duplicate snowpack logs
* Fix test to wait on expected messages
* Update the snowpack/plugin-vue
* Add changeset
* Debugging
* Skip the logging test on windows :(
* arg
* fix(vscode): Markdown frontmatter should use TSX, not YAML
* test: add test for #153
* chore: bump deps
* chore: update to use @astrojs scope
* fix: Markdown parse error when only child is `{expression}`
* fix: update renderer edge cases
* fix: failing test
* fix: update renderer
* Remove create-astro from workspace
* Improve contrast ratio
* Swap blank template for blog template
* Remove counter components from blog template
* Use `latest` astro version
