Alex Lohr
Alex Lohr
If that is the case then let us remove the script and add the ability to collect coverage to the documentation.
I have [documented the process](https://dev.to/lexlohr/using-solid-start-with-github-pages-3iok).
There's no native path conversion in node, unfortunately.
I too would prefer integration classes, i.e. an option for styling (tailwind, vanilla extract, uno-css, solid-styled, CSS modules), testing (vitest, jest, uvu, none), linting (eslint+solid plugin, none), etc. However, it's...
You need an additional "solid" export with the JSX untranspiled so the framework can pick it up from there.
Sorry, I missed this comment. This was more a question of convenience. Where to put the props?
Thanks for the information. The error is most likely either in the template or in vite-plugin-solid. I will have a closer look in any case.
Unfortunately, I cannot reproduce this error; however, using useNavigate() does not work at all; it claims it was used outside of a route context. I'm still investiaging.
Adding an ``-tag (with noScroll to avoid an error due to scrolling not being supported by jsdom) inside a Route worked for my, though. The investigation continues.
It's officially released by now. I rebased to current master.