publish VS next.js

I feel the exact same way. I have some plugin ideas to smooth over the process as well. The built in publishing feature is a little rough and not optimized at all. I get the impression that logseq is investing a lot more energy on their own hosted solution than the self hosted publishing right now.

Despite the downsides, as someone who spent way too much time tweaking their own static site, it's really nice to be able to do just write and organize everything inside logseq and push my thoughts up at the end of the day. I was spending way to much time configuring and polishing the static site instead of just getting the notes out there.

Logseq had a tool to publish your notes as a static site, but it's out of date now unfortunately. https://github.com/logseq/publish

Since Logseq handles everything with plain text, some people are just generating a static site from those files directly, but you lose some of the advanced logseq features. I'm looking into doing this to make a "light" version of the notes as a static html site.

While it's technically possible to do things like compile React entirely out of an exported NextJS site, it's far from trivial and doesn't fit most usage very well. It's certainly a harder mental model at the very least.

Disable all your chrome extensions. As recommended here https://github.com/zeit/next.js/issues/10246

Link: https://github.com/zeit/next.js/blob/canary/examples/with-graphql-faunadb/lib/useFetch.js

import React, { Component, Fragment } from 'react';import { withRouter } from 'next/router';import 'isomorphic-unfetch';class post extends Component { static async getInitialProps({ req }) { try { const res = await fetch(`http://localhost/api/posts/${req.params.postslug}`, { method: 'GET', // *GET, POST, PUT, DELETE, etc. mode: 'cors', // no-cors, cors, *same-origin }); const json = await res.json(); return { data: json.data }; } catch (err) { console.log('err'); } } render() { const { data } = this.props; return ( ); }}export default withRouter(post); I have already checked the next.js docs and it has this implementation which uses the node http module. I implemented this code on express by copying some parts from the documentation example. However it still seems to cause a page reload when i go to the article page using a .

next.js

NextJS: 8.0.3

Read more one the github issue

import React from 'react';import PropTypes from 'prop-types';class VerticalSlider extends React.Component { constructor(props) { super(props); this.ScrollMagic = null; this.controller = null; this.scenes = []; this.container = React.createRef(); } componentDidMount() { if (this.container.current) { // Why "require" here? // https://github.com/zeit/next.js/issues/219#issuecomment-393939863 // We can't render the component server-side, but we will still render // the HTML // eslint-disable-next-line global-require this.ScrollMagic = require('scrollmagic'); this.initScroller(); } } componentWillUnmount() { this.scenes.forEach(scene => { scene.destroy(); }); this.controller.destroy(); this.scenes = []; this.controller = null; } initScroller() { try { this.controller = new this.ScrollMagic.Controller(); if (this.container.current !== null && this.container.current.children) { [...this.container.current.children].forEach(children => { const scene = new this.ScrollMagic.Scene({ triggerElement: children, duration: window.innerHeight * 1.5, triggerHook: 0, reverse: true }); scene.setPin(children); this.scenes.push(scene); }); this.controller.addScene(this.scenes); } } catch (e) { console.log(e); } } render() { return (