hi, when i clone this repo and connect it to my mongodb instance, i can successfully sign up and it will sign me in properly the first time. it seems like the signup function in the users controller is what is called when the user is first signing up to log them in. i'm able to log out successfully from here. when i log in again (and my user already exists) it looks like you log in via the login function in the users controller. it logs me in successfully, but when i try to log out, i get this error and can't figure out where headers are being set after they're already sent to the client.

wait  - compiling...
event - compiled successfully
Error [ERR_HTTP_HEADERS_SENT]: Cannot set headers after they are sent to the client
    at ServerResponse.setHeader (_http_outgoing.js:558:11)
    at DevServer.sendHTML (/Users//Documents//temp/notion-clone/frontend/node_modules/next/dist/server/next-dev-server.js:35:5)
    at DevServer.render (/Users//Documents//temp/notion-clone/frontend/node_modules/next/dist/next-server/server/next-server.js:56:37)
    at async Object.fn (/Users//Documents//temp/notion-clone/frontend/node_modules/next/dist/next-server/server/next-server.js:32:556)
    at async Router.execute (/Users//Documents//temp/notion-clone/frontend/node_modules/next/dist/next-server/server/router.js:23:67)
    at async DevServer.run (/Users//Documents//temp/notion-clone/frontend/node_modules/next/dist/next-server/server/next-server.js:49:656)
    at async DevServer.handleRequest (/Users//Documents//temp/notion-clone/frontend/node_modules/next/dist/next-server/server/next-server.js:20:388) {
  code: 'ERR_HTTP_HEADERS_SENT'
}
events.js:292
      throw er; // Unhandled 'error' event
      ^

Error [ERR_STREAM_WRITE_AFTER_END]: write after end
    at writeAfterEnd (_http_outgoing.js:668:15)
    at ServerResponse.end (_http_outgoing.js:788:7)
    at ServerResponse.end (/Users//Documents//temp/notion-clone/frontend/node_modules/next/dist/compiled/compression/index.js:1:142407)
    at DevServer.handleRequest (/Users//Documents//temp/notion-clone/frontend/node_modules/next/dist/next-server/server/next-server.js:20:476)
Emitted 'error' event on ServerResponse instance at:
    at writeAfterEndNT (_http_outgoing.js:727:7)
    at processTicksAndRejections (internal/process/task_queues.js:81:21) {
  code: 'ERR_STREAM_WRITE_AFTER_END'
}

i noticed this isn't an issue on the deployed site link in this repo, am i missing something?

PS C:\notion-clone\frontend> npm start

[email protected] start next start -p $PORT

Error: Could not find a valid build in the 'C:\notion-clone\frontend.next' directory! Try building your app with 'next build' before starting the server. at Server.readBuildId (C:\notion-clone\frontend\node_modules\next\dist\next-server\server\next-server.js:120:355) at new Server (C:\notion-clone\frontend\node_modules\next\dist\next-server\server\next-server.js:3:120) at createServer (C:\notion-clone\frontend\node_modules\next\dist\server\next.js:2:638) at start (C:\notion-clone\frontend\node_modules\next\dist\server\lib\start-server.js:1:323) at nextStart (C:\notion-clone\frontend\node_modules\next\dist\cli\next-start.js:19:125) at C:\notion-clone\frontend\node_modules\next\dist\bin\next:26:341 PS C:\notion-clone\frontend>

Simple question

• Why not contributing to https://editorjs.io/ ?

• [x] They still have a wide community

• [x] They support many plugins

• [x] They are still used by many production projects

Hi, these new features are very useful for developers..

I have added a feature which will display status of sever running on port and then it will check connection with database... if there any error encounter while connecting with DB, it display it on console......

Both backend and frontend directories are missing .env.sample and it is a hurdle to start the app on my localhost. I'd be a great help if you could add a .env.sample in your project to help us get started quickly.

Thanks!

Very nice project and serious effort, congrats.

1. In the frontend/pages/account.js in getServerSideProps() why do you make http call when that function runs on server and it can query database directly?

export const getServerSideProps = async (context) => {
  ...
  try {
    const response = await fetch(
      `${process.env.NEXT_PUBLIC_API}/users/account`,

2. In the frontend/context/UserContext.js why do you create 2 separate contexts

<UserStateContext.Provider value={state}>
  <UserDispatchContext.Provider value={dispatch}>

instead of one?

<UserContext.Provider value={{state, dispatch}}>

Steps to recreate:

1. Select the page title region
2. Type "/" and then select the image type
3. When the image selection window pops up, select "Cancel" or close the window
4. The page becomes unusable

Steps to recreate:

1. Go to the demo website which will automatically create a new page
2. Instead of entering a page title, press backspace

Upon pressing backspace, all functionality of the page is removed. A new title cannot be added and no contents on the page can be created

Thanks for the tutorial. It was excellent. I am coming back to JavaScript and React after a hiatus of 4.5 years.

I had to change the following line:

import matchSorter from "match-sorter";

to import { matchSorter } from "match-sorter";

I am on version match-sorter 6.3.1 (the latest version)

hello, dev bro. If i click on the page freely, hopefully, there will add a block automatically. i should repeatedly click "enter" to go to the place where i prefer to. 😂