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
Inspired by next's approach, it would be a useful convenience to auto-serve everything in the /pages directory. It would mean being able to drop the line on the README:
And even the use of express (regular http server should be fine).
There is a bit of disconnect in next between the actual pages and the react component's it exports. It abstracts a bit too highly, then offers a Head component to tweak the <head>. I think in our case it should be fine to just statically serve this directory rather than trying to interpret a component as a page. Using a custom element in HTML is super trivial:
<scriptsrc="ripple.js"></script><my-app></my-app>
The text was updated successfully, but these errors were encountered:
Inspired by next's approach, it would be a useful convenience to auto-serve everything in the
/pagesdirectory. It would mean being able to drop the line on the README:- app.get('/*', (req, res) => res.sendFile(__dirname+'/index.html'))And even the use of express (regular http server should be fine).
There is a bit of disconnect in next between the actual pages and the react component's it exports. It abstracts a bit too highly, then offers a
Headcomponent to tweak the<head>. I think in our case it should be fine to just statically serve this directory rather than trying to interpret a component as a page. Using a custom element in HTML is super trivial:The text was updated successfully, but these errors were encountered: