#no results
1 messages · Page 1 of 1 (latest)
hmm, open the package.json and add this:"deploy": "node deploy-commands.js" under scripts
that's my npm run build
wouldn't that just run node deploy-commands which has already been shown to not work?
im going off what i use on gitbash
oh you online host? i local host my ones, NPM is in gitbash using a command shell
the best i can think of is attempting to run the file like index
or main howwhere you named your brain file
it is index
hmm
here's what happened
with index
actually this should be something else
no results
so you get nothing with node index.js?
did you try using the hint that shows on the log? at any point
what do you have in your index to connect to the client?
i'll share the repl
you appear to be missing (or its hidden from public view) the npm files for the node_global folder
nope
anything pop up?
nope
im not that familiar to repl, ill see if i can find a recent review
try adding to the top of the index file:
const express = require('express');
const app = express();
const port = 3000;
app.get('/', (req, res) => res.send('Hello World!'));
app.listen(port, () => console.log(`Example app listening at http://localhost:${port}`));
source: https://dev.to/fizal619/so-you-want-to-make-a-discord-bot-4f0n some parts look a bit outdated for djs terms but the top section may work
that may work after it connects to the server on repl
works now :D
great!
i'm going to test it out rn
if you go on the link it has a section on keeping it online 24/7
if i update to i have to pause it