Closed TheShadowGamer closed 3 years ago
Path is sometimes used, but its never installed with npm i
. An example would be line 3 of approve-join.js
. I have fixed that in my last commit.
Path is sometimes used, but its never installed with
npm i
. An example would be line 3 ofapprove-join.js
. I have fixed that in my last commit.
Because it's built into Node.js. 🙃
Weird, as it errored when I tried using require path
for something I'll PR soon. Still safe to have it in the package.json in my opinion, but that is up to you.
Wouldn't it be less safe? Because then you're relying on the people who have the npm package "path" to keep it 100% updated to the built in package.
I suppose. I'm not sure why path would fail to require if it is built into Node.js.
Anyways, can you please remove it from the package.json so I can merge this pull request? Thanks.
Alright will do.
Throughout lines 28-60, you attempt to use
client.config
which you cannot use since it is not defined until later. The fix would be to move theclient.config = config
higher up, as I have done.