Cannot read properties of null (reading 'querySelector') about destack HOT 13 CLOSED

@Eesssn

It would be helpful to provide a repository or a Codesandbox that reproduces the error. If the error is on a public one just share the url.

from destack.

Hello Great Work,

Followed instructions in the https://www.youtube.com/watch?v=zJoaxMX7AKM&ab_channel=AndreasTzionis

You can check the repo: https://github.com/Battlelamb/destack-test

All the best

from destack.

Env:

{
npm: '8.11.0',
node: '16.15.1',
v8: '9.4.146.24-node.21',
uv: '1.43.0',
zlib: '1.2.11',
brotli: '1.0.9',
ares: '1.18.1',
modules: '93',
nghttp2: '1.47.0',
napi: '8',
llhttp: '6.0.4',
openssl: '1.1.1o+quic',
cldr: '40.0',
icu: '70.1',
tz: '2021a3',
unicode: '14.0',
ngtcp2: '0.1.0-DEV',
nghttp3: '0.1.0-DEV'
}

from destack.

Hey @Battlelamb,

Is this about the problem mentioned in the summary of the issue or about something else?

from destack.

Hey,

Thnx for the replay

Yes it is the same issue

from destack.

from destack.

@Battlelamb

I managed to reproduce this. Thanks for validating and sharing the repo.

If you don't mind leaving it public for the next few days it would help to fix it.

from destack.

Great, thanks, by all means :)

from destack.

@Battlelamb @Eesssn

I think I got to the bottom of this. It seems React 18 introduces some changes with StrictMode to ensure useEffect is used correctly.

A quick dirty fix will be to set reactStrictMode to false in your next.config.js.

Regardless, I will deploy a fix sometime soon with version 0.11.4.

You can read more here:

1. facebook/react#24502
2. https://reactjs.org/docs/strict-mode.html#detecting-unexpected-side-effects

from destack.

Great, I will check and get back to you.

Thnx a lot :)

from destack.

Yes, it is working right now.

Also I tried the react version it won't start.

Should I start a new issue? or I made something wrong? :)

You can check the public repo here: https://github.com/Battlelamb/destack-react-starter

Error:
Debugger attached.

[email protected] start
destack -d "react-scripts start"

Debugger attached.
Waiting for the debugger to disconnect...
events.js:377
throw er; // Unhandled 'error' event
^

Error: spawn concurrently ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:277:19)
at onErrorNT (internal/child_process.js:472:16)
at processTicksAndRejections (internal/process/task_queues.js:82:21)
Emitted 'error' event on ChildProcess instance at:
at Process.ChildProcess._handle.onexit (internal/child_process.js:283:12)
at onErrorNT (internal/child_process.js:472:16)
at processTicksAndRejections (internal/process/task_queues.js:82:21) {
errno: -4058,
code: 'ENOENT',
syscall: 'spawn concurrently',
path: 'concurrently',
spawnargs: [
nodemon --watch "../../lib/destack/server" --ext "ts,json" --exec "ts-node -O '{\\"module\\":\\"commonjs\\"}' ../../lib/destack/server/react.ts",
'react-scripts start'
]
}
Waiting for the debugger to disconnect...

from destack.

The problem is gone but when I designed a site, it didn't save.

After "npm run build", it tried to start with "npm start", but there was only white blank screen.

Updating the public repo :))

from destack.

Hey @Battlelamb,

I just fixed a couple of issues with Windows. The version 0.12.0 is now up on NPM and you can try it with npm i destack@latest or using destack-react-starter.

Let me know if this fixes it.

from destack.