I keep getting errors with Gridsome starters when executing the gridsome develop command.
I've tried the default starter that Grisdome recommends and now the Contentful Starter so far and errors keep showing up in the terminal.
Here is the error I get with the Contentful starter:
Initializing plugins...
Error: Request failed with status code 404
at createError (/var/www/public/my-project/node_modules/contentful/dist/contentful.node.js:886:15)
at settle (/var/www/public/my-project/node_modules/contentful/dist/contentful.node.js:1049:12)
at Unzip.handleStreamEnd (/var/www/public/my-project/node_modules/contentful/dist/contentful.node.js:294:11)
at Unzip.emit (events.js:215:7)
at endReadableNT (_stream_readable.js:1183:12)
at processTicksAndRejections (internal/process/task_queues.js:80:21)
And here is the error from the default starter:
Error
at afterWriteDispatched (internal/stream_base_commons.js:150:25)
at writeGeneric (internal/stream_base_commons.js:141:3)
at Socket._writeGeneric (net.js:770:11)
at Socket._write (net.js:782:8)
at doWrite (_stream_writable.js:431:12)
at writeOrBuffer (_stream_writable.js:415:5)
at Socket.Writable.write (_stream_writable.js:305:11)
at Socket.Writable.end (_stream_writable.js:594:10)
at Socket.end (net.js:574:31)
at handleInput (/var/www/public/myblog/node_modules/imagemin-pngquant/node_modules/execa/index.js:87:17)
Related
I downloaded a bot that periodically modifies the Minecraft server status on Discord from Github, and this error pops up. How can I fix it?
C:\Users\Administrator\Downloads\minecraft-bot-main\events\interactionCreate.js:4
if (interaction.type !== InteractionType.ApplicationCommand) return;
^
TypeError: Cannot read properties of undefined (reading 'ApplicationCommand')
at module.exports (C:\Users\Administrator\Downloads\minecraft-bot-main\events\interactionCreate.js:4:46)
at Client.emit (node:events:513:28)
at InteractionCreateAction.handle (C:\Users\Administrator\Downloads\minecraft-bot-main\node_modules\discord.js\src\client\actions\InteractionCreate.js:83:12)
at module.exports [as INTERACTION_CREATE] (C:\Users\Administrator\Downloads\minecraft-bot-main\node_modules\discord.js\src\client\websocket\handlers\INTERACTION_CREATE.js:4:36)
at WebSocketManager.handlePacket (C:\Users\Administrator\Downloads\minecraft-bot-main\node_modules\discord.js\src\client\websocket\WebSocketManager.js:346:31)
at WebSocketShard.onPacket (C:\Users\Administrator\Downloads\minecraft-bot-main\node_modules\discord.js\src\client\websocket\WebSocketShard.js:478:22)
at WebSocketShard.onMessage (C:\Users\Administrator\Downloads\minecraft-bot-main\node_modules\discord.js\src\client\websocket\WebSocketShard.js:317:10)
at callListener (C:\Users\Administrator\Downloads\minecraft-bot-main\node_modules\ws\lib\event-target.js:290:14)
at WebSocket.onMessage (C:\Users\Administrator\Downloads\minecraft-bot-main\node_modules\ws\lib\event-target.js:209:9)
at WebSocket.emit (node:events:513:28)
Node.js v18.8.0
Reinstall node 18.14.0 to 18.8.0 and command 'npm insatll'
I'm trying to run my project on a server Part of the project is an auto-puppeteer browser and I'm running so a browser opening error is thrown
Does anyone have a solution for this?
Attaches an error
/app/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:241
reject(new Error([
^
Error: Failed to launch the browser process!
/app/node_modules/puppeteer/.local-chromium/linux-982053/chrome-linux/chrome: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory
TROUBLESHOOTING: https://github.com/.../blob/main/docs/troubleshooting.md
at onClose (/app/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:241:20)
at Interface. (/app/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:231:68)
at Interface.emit (node:events:539:35)
at Interface.close (node:readline:586:8)
at Socket.onend (node:readline:277:10)
at Socket.emit (node:events:539:35)
at endReadableNT (node:internal/streams/readable:1345:12)
at processTicksAndRejections (node:internal/process/task_queues:83:21)
You need to add the Puppeteer-Heroku-Buildpack
https://github.com/jontewks/puppeteer-heroku-buildpack
I have a puppeteer script I run to reboot my modem. It has worked for I guess about a year with no problem. 5 days ago it stopped working. I was looking into it and realized that I am getting errors I didn't used to get when running it and the script fails. The thing is I didn't change anything. As far as I can see, the HTML hasn't changed either yet it is failing. So I wonder if there is a bug in chromium or puppeteer or if it handles things differently somehow?
Here's a codepen with https://codepen.io/michaelbierman/pen/qQjdYR
HTML page
puppeteer script
errors
ERROR OUTPUT
Thursday 11/15/2018 11:14:04, Login...
Unhandled Rejection at: Promise (new page) Promise {
Error: No node found for selector: #id_username
at assert (/Users/bierman/Documents/Applications/bin/arris/node_modules/puppeteer/lib/helper.js:278:11)
at Frame.type (/Users/bierman/Documents/Applications/bin/arris/node_modules/puppeteer/lib/FrameManager.js:771:5)
at
at process._tickCallback (internal/process/next_tick.js:188:7)
-- ASYNC --
at Frame. (/Users/bierman/Documents/Applications/bin/arris/node_modules/puppeteer/lib/helper.js:144:27)
at Page.type (/Users/bierman/Documents/Applications/bin/arris/node_modules/puppeteer/lib/Page.js:971:29)
at /Users/bierman/Documents/Applications/bin/arris/arristest.js:49:13
at
at process._tickCallback (internal/process/next_tick.js:188:7) } reason: Error: No node found for selector: #id_username
at assert (/Users/bierman/Documents/Applications/bin/arris/node_modules/puppeteer/lib/helper.js:278:11)
at Frame.type (/Users/bierman/Documents/Applications/bin/arris/node_modules/puppeteer/lib/FrameManager.js:771:5)
at
at process._tickCallback (internal/process/next_tick.js:188:7)
-- ASYNC --
at Frame. (/Users/bierman/Documents/Applications/bin/arris/node_modules/puppeteer/lib/helper.js:144:27)
at Page.type (/Users/bierman/Documents/Applications/bin/arris/node_modules/puppeteer/lib/Page.js:971:29)
at /Users/bierman/Documents/Applications/bin/arris/arristest.js:49:13
at
at process._tickCallback (internal/process/next_tick.js:188:7)
/Users/bierman/Documents/Applications/bin/arris/arristest.js:29
browser.close();
^
ReferenceError: browser is not defined
at process.on (/Users/bierman/Documents/Applications/bin/arris/arristest.js:29:2)
at emitTwo (events.js:126:13)
at process.emit (events.js:214:7)
at emitPendingUnhandledRejections (internal/process/promises.js:108:22)
at process._tickCallback (internal/process/next_tick.js:189:7)
BigMac:bin michael$ /usr/local/bin/node /Users/bierman/Documents/Applications/bin/arris/arristest.js
Thursday 11/15/2018 11:20:29, Login...
Thursday 11/15/2018 11:20:36, Go to home...
Unhandled Rejection at: Promise (new page) Promise {
Error: No node found for selector: #alertExitButton
at assert (/Users/bierman/Documents/Applications/bin/arris/node_modules/puppeteer/lib/helper.js:278:11)
at Frame.click (/Users/bierman/Documents/Applications/bin/arris/node_modules/puppeteer/lib/FrameManager.js:704:5)
at
at process._tickCallback (internal/process/next_tick.js:188:7)
-- ASYNC --
at Frame. (/Users/bierman/Documents/Applications/bin/arris/node_modules/puppeteer/lib/helper.js:144:27)
at Page.click (/Users/bierman/Documents/Applications/bin/arris/node_modules/puppeteer/lib/Page.js:932:29)
at /Users/bierman/Documents/Applications/bin/arris/arristest.js:62:13
at
at process._tickCallback (internal/process/next_tick.js:188:7) } reason: Error: No node found for selector: #alertExitButton
at assert (/Users/bierman/Documents/Applications/bin/arris/node_modules/puppeteer/lib/helper.js:278:11)
at Frame.click (/Users/bierman/Documents/Applications/bin/arris/node_modules/puppeteer/lib/FrameManager.js:704:5)
at
at process._tickCallback (internal/process/next_tick.js:188:7)
-- ASYNC --
at Frame. (/Users/bierman/Documents/Applications/bin/arris/node_modules/puppeteer/lib/helper.js:144:27)
at Page.click (/Users/bierman/Documents/Applications/bin/arris/node_modules/puppeteer/lib/Page.js:932:29)
at /Users/bierman/Documents/Applications/bin/arris/arristest.js:62:13
at
at process._tickCallback (internal/process/next_tick.js:188:7)
/Users/bierman/Documents/Applications/bin/arris/arristest.js:29
browser.close();
^
ReferenceError: browser is not defined
at process.on (/Users/bierman/Documents/Applications/bin/arris/arristest.js:29:2)
at emitTwo (events.js:126:13)
at process.emit (events.js:214:7)
at emitPendingUnhandledRejections (internal/process/promises.js:108:22)
at process._tickCallback (internal/process/next_tick.js:189:7)
Try this:
npm uninstall chromium
npm uninstall puppeteer
npm i chromium#1
npm i puppeteer
I am getting the below error while trying to run Mocha JS test case which runs npm request-promise to call a REST service. I was able to connect to the REST URI endpoint through ARC client bur it failed with below error while running through organization's proxy-
RequestError: Error: connect ETIMEDOUT SERVER_IP:SERVER_PORT
at new RequestError (<Some_Path>\errors.js:14:15)
at Request.plumbing.callback (<Some_Path>\plumbing.js:87:29)
at Request.RP$callback [as _callback] (<Some_Path>\plumbing.js:46:31)
at self.callback (<Some_Path>\request.js:188:22)
at Request.onRequestError (<Some_Path>\request\request.js:884:8)
at TLSSocket.socketErrorListener (_http_client.js:309:9)
at emitErrorNT (net.js:1277:8)
at _combinedTickCallback (internal/process/next_tick.js:80:11)
at process._tickCallback (internal/process/next_tick.js:104:9)
I fixed this issue with adding the following in the request-promise options-
proxy:'http://PROXY_SERVER_IP:PORT#'
I hope this helps.
Cheers,
Kunal
This worked for me
var request = require('request-promise').defaults({
proxy:'http://username:password#host:port',
strictSSL :false
});
I am trying to install reaction commerce (reactioncommerce.com) in Google Compute engine with f1-micro (1 vCPU, 0.6 GB memory) server configuration. I am getting while starting the reaction commerce in gcloud shell.
Please guide me what i should do.
zenmonk#eshop::~/reaction reaction init shop
Cloning the master branch of Reaction from Github...
Cloning into 'shop'...
Installing NPM packages...
npm WARN deprecated tough-cookie#2.2.2: ReDoS vulnerability parsing Set-Cookie https://nodesecurity.io/advisories/130
dtrace-provider#0.6.0 install /home/zenmonk/reaction/shop/node_modules/dtrace-provider
node scripts/install.js
fibers#1.0.13 install /home/zenmonk/reaction/shop/node_modules/fibers
node build.js || nodejs build.js
linux-x64-v8-4.5 exists; testing
Binary is fine; exiting
reaction#0.14.2 postinstall /home/zenmonk/reaction/shop
.reaction/scripts/postinstall.sh
reaction#0.14.2 /home/zenmonk/reaction/shop
Reaction successfully installed!
To start your Reaction instance, just run:
cd shop
reaction
zenmonk#eshop#:~/reaction/shop$ reaction
Using settings file at settings/dev.settings.json
Setting up plugin imports...
[[[[[ ~/reaction/shop ]]]]]
=> Started proxy.
=> Started MongoDB.
buffer.js:25
const ui8 = new Uint8Array(size);
^
RangeError: Invalid array buffer length
at new ArrayBuffer (native)
at new Uint8Array (native)
at createBuffer (buffer.js:25:17)
at allocate (buffer.js:96:12)
at new Buffer (buffer.js:56:12)
at increaseBufferIfNecessary (/home/zenmonk/.meteor/packages/meteor-tool/.1.4.0-1.13j49n2++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/lib/node_modules/stream-buffers/lib/writable_streambuffer.js:58:23)
at [object Object].write (/home/zenmonk/.meteor/packages/meteor-tool/.1.4.0-1.13j49n2++os.linux.x8664+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/lib/node_modules/stream-buffers/lib/writable_streambuffer.js:65:5)
at doWrite (streamwritable.js:300:12)
at writeOrBuffer (streamwritable.js:286:5)
at [object Object].Writable.write (streamwritable.js:214:11)
at Request.ondata (stream.js:31:26)
at emitOne (events.js:82:20)
at Request.emit (events.js:169:7)
at IncomingMessage. (/home/zenmonk/.meteor/packages/meteor-tool/.1.4.0-1.13j49n2++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/lib/node_modules/request/request.js:1255:12)
at emitOne (events.js:77:13)
at IncomingMessage.emit (events.js:169:7)
at readableAddChunk (streamreadable.js:153:18)
at IncomingMessage.Readable.push (streamreadable.js:111:10)
at HTTPParser.parserOnBody (httpcommon.js:124:22)
at TLSSocket.socketOnData (httpclient.js:320:20)
at emitOne (events.js:77:13)
at TLSSocket.emit (events.js:169:7)
at readableAddChunk (streamreadable.js:153:18)
at TLSSocket.Readable.push (streamreadable.js:111:10)
at TLSWrap.onread (net.js:536:20)
This was wrong with me too and I solved the problem by increasing the computer's memory
this issue is identical to your
RangeError: Invalid array buffer length - Meteor JS