Docsify packages from packager throw errors on fresh repl

Hello all, thanks for taking the time to help.

I have a fresh repl with only text changes in the HTML head and body. I used packager to install docsify as I want to learn how to use it and create a tutorial as I work. However, when I add the packages to my project and run the project the console shows it throws an error and I am unable to continue. The original docsify package alone also throws error. With the other packages, this error gets thrown 3-5 times.

Error: null   https://replco.util.repl.co/devtools/devtools.js:74
at t.formatMsg (https://replco.util.repl.co/devtools/devtools.js:74:4944)
at new t (https://replco.util.repl.co/devtools/devtools.js:74:1602)
at t.insertSync (https://replco.util.repl.co/devtools/devtools.js:97:16960)
at https://replco.util.repl.co/devtools/devtools.js:97:18563
Error: null   https://replco.util.repl.co/devtools/devtools.js:74
Error: null   https://replco.util.repl.co/devtools/devtools.js:74
Error: null   https://replco.util.repl.co/devtools/devtools.js:74

It appears that a null value is being sent to devtools.js which appears to be a replit script. No idea how to move forward from here.

EDIT:
I went to the devtools.js file and searched for t.formatMsg and that particular string does not appear in the entire document! I tried going to it again and it looks like it is no longer available – but there was a ct.formatMsg() string I found. No idea what to make of that.

Repl URL: Docsify-Tutorial - Replit

Hi @GeorgeSchafer thanks for your message.

I’ve tried to replicate your issue and do not get any errors. Can you please try again with a fresh repl and let me know if the same error occurs?

Hi Ian, thanks for your help. I just tried again on a fresh repl, I touched literally nothing except the packager to add the packages. Same result.

I am working on a Mac with Google Chrome. I don’t see why that should matter, but I am including it just in case.

1 Like

Thanks @GeorgeSchafer I think issue might be with the Docsify Copy Code module. I’ve raised a helpdesk call with Loading... - Form by Asana and linked to this Discourse post. If I get any more information / queries back I’ll post them here.

Hello @GeorgeSchafer!

It looks like the repl might’ve been deleted. Could you please recreate the repl so we can take a look?

1 Like

Yes, I just recreated it in docsify-package-error.

Sorry about that, I migrated my GitHub to another account and it threw everything into chaos. I tried to update the link in the original post, but it looks like I don’t have the option.

No problem! We will take a look and will follow up soon!

We aren’t able to reproduce the error on our end:

It looks like this might be an issue with your browser or network. Would you mind sending me your browser and OS info (I recommend this site to get the info).

Also, could you try viewing the repl using a private window or a different browser to see if that helps?

Your User Agent is:
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36

Interesting. I ran the repl in InCognito mode and I received 10 errors in the console (8x are the same error).

docsify.min.js:1 Uncaught TypeError: Cannot read properties of null (reading 'querySelector')
    at b (docsify.min.js:1:1212)
    at Ee (docsify.min.js:1:29653)
    at docsify.min.js:1:101932
b @ docsify.min.js:1
Ee @ docsify.min.js:1
(anonymous) @ docsify.min.js:1
docsify.min.js:1 Uncaught TypeError: Cannot read properties of null (reading 'querySelector')
    at b (docsify.min.js:1:1212)
    at Ee (docsify.min.js:1:29653)
    at docsify.min.js:1:101932
b @ docsify.min.js:1
Ee @ docsify.min.js:1
(anonymous) @ docsify.min.js:1
docsify.min.js:1 Uncaught TypeError: Cannot read properties of null (reading 'querySelector')
    at b (docsify.min.js:1:1212)
    at Ee (docsify.min.js:1:29653)
    at docsify.min.js:1:101932
b @ docsify.min.js:1
Ee @ docsify.min.js:1
(anonymous) @ docsify.min.js:1
docsify.min.js:1 Uncaught TypeError: Cannot read properties of null (reading 'querySelector')
    at b (docsify.min.js:1:1212)
    at Ee (docsify.min.js:1:29653)
    at docsify.min.js:1:101932
b @ docsify.min.js:1
Ee @ docsify.min.js:1
(anonymous) @ docsify.min.js:1
docsify.min.js:1 Uncaught TypeError: Cannot read properties of null (reading 'querySelector')
    at b (docsify.min.js:1:1212)
    at Ee (docsify.min.js:1:29653)
    at docsify.min.js:1:101932
b @ docsify.min.js:1
Ee @ docsify.min.js:1
(anonymous) @ docsify.min.js:1
docsify.min.js:1 Uncaught TypeError: Cannot read properties of null (reading 'querySelector')
    at b (docsify.min.js:1:1212)
    at Ee (docsify.min.js:1:29653)
    at docsify.min.js:1:101932
b @ docsify.min.js:1
Ee @ docsify.min.js:1
(anonymous) @ docsify.min.js:1
docsify.min.js:1 Uncaught TypeError: Cannot read properties of null (reading 'querySelector')
    at b (docsify.min.js:1:1212)
    at Ee (docsify.min.js:1:29653)
    at docsify.min.js:1:101932
b @ docsify.min.js:1
Ee @ docsify.min.js:1
(anonymous) @ docsify.min.js:1
docsify.min.js:1 Uncaught TypeError: Cannot read properties of null (reading 'querySelector')
    at b (docsify.min.js:1:1212)
    at Ee (docsify.min.js:1:29653)
    at docsify.min.js:1:101932
b @ docsify.min.js:1
Ee @ docsify.min.js:1
(anonymous) @ docsify.min.js:1

Thanks! After some digging, I could reproduce the issue on Chrome and noticed that when I tried on Firefox, it flashed the error but then worked normally. We are tracking this bug regarding the devtools, although this specific issue might be related to an error with Docsify.

When I opened the repl’s output in a new tab, I noticed that it was producing a few errors:

I’m not familiar with Docsify, but could this be an issue related to the setup of the script?

1 Like

It’s hard to tell. I am a beginner with Docsify and I tended to build a tutorial as I learned how things worked.

I ended up installing via Node on my computer and I didn’t run into any trouble.

I’m so sorry I missed this! I’ll continue investigating and see if I can find where the issue might be!

We have finally gotten to the bottom of the issue where errors in the console were pointing to devtools instead of the actual error. We released a fix for this yesterday, so would you mind checking to see if you’re running into any other issues?

Hello Shane, sorry I wasn’t able to get to this sooner. I just tried to do this, but I got an error from NPM.

Sorry about that! That error is because the “Console” tab is a NodeJS REPL, used for running arbitrary NodeJS (such as console.log("hello world!")). Instead, you can run the NPM commands in the “Shell” tab of your repl.

1 Like