Develop Reference

Deploying contracts with truffle error: Contracts.compile is not a function

I am running through smart contract creation and deployment from scratch to reaffirm knowledge in the fundamentals of contract creation.
After successfully creating local accounts via $truffle develop and jumping into the development console via truffle console --network development (development can be replaced by whichever network name you have defined in truffle.js), running deploy --compile-all --reset returns the following error;
TypeError: Contracts.compile is not a function
at Object.run (/usr/local/lib/node_modules/truffle/build/cli.bundled.js:202236:15)
at Command.run (/usr/local/lib/node_modules/truffle/build/cli.bundled.js:160767:20)
at Console.interpret (/usr/local/lib/node_modules/truffle/build/cli.bundled.js:202606:25)
at ReplManager.interpret (/usr/local/lib/node_modules/truffle/build/cli.bundled.js:203345:18)
at bound (node:domain:421:15)
at REPLServer.runBound [as eval] (node:domain:432:12)
at REPLServer.onLine (node:repl:893:10)
at REPLServer.emit (node:events:526:28)
at REPLServer.emit (node:domain:475:12)
at REPLServer.Interface._onLine (node:readline:487:10)
Any help would be much appreciated.

How to run "vue ui" with Node.js v17.2.0?

I need to use "vue ui" in my project but resently I have update node 14 to Node.js v17.2.0 and now I can't open Vue GUI. Still Ihave a problem:
at Object.readdirSync (node:fs:1390:3)
at exports.readdir (/usr/local/lib/node_modules/#vue/cli/node_modules/#mrmlnc/readdir-enhanced/lib/sync/fs.js:18:20)
at Object.safeCall [as safe] (/usr/local/lib/node_modules/#vue/cli/node_modules/#mrmlnc/readdir-enhanced/lib/call.js:24:8)
at DirectoryReader.readNextDirectory (/usr/local/lib/node_modules/#vue/cli/node_modules/#mrmlnc/readdir-enhanced/lib/directory-reader.js:78:10)
at Readable.DirectoryReader.stream._read (/usr/local/lib/node_modules/#vue/cli/node_modules/#mrmlnc/readdir-enhanced/lib/directory-reader.js:57:18)
at Readable.read (node:internal/streams/readable:496:27)
at readdirSync (/usr/local/lib/node_modules/#vue/cli/node_modules/#mrmlnc/readdir-enhanced/lib/sync/index.js:27:21)
at Function.readdirSyncStat (/usr/local/lib/node_modules/#vue/cli/node_modules/#mrmlnc/readdir-enhanced/lib/index.js:34:10)
at ReaderSync.dynamicApi (/usr/local/lib/node_modules/#vue/cli/node_modules/fast-glob/out/providers/reader-sync.js:64:24)
at ReaderSync.api (/usr/local/lib/node_modules/#vue/cli/node_modules/fast-glob/out/providers/reader-sync.js:56:25)
Emitted 'error' event on Readable instance at:
at emitErrorNT (node:internal/streams/destroy:164:8)
at emitErrorCloseNT (node:internal/streams/destroy:129:3)
at processTicksAndRejections (node:internal/process/task_queues:83:21) {
errno: -2,
syscall: 'scandir',
code: 'ENOENT',
path: '/Users/ewakadziolka/Desktop/vue/emmaus/node_modules/#vue/cli-service/locales'
}
directory that coud be founded is my lastest projest that I used Vue GUI with node 14 yet not new one where I want to use Vue GUI.
Do you have any solution?
Thanks

I've decided to install node v16.13.1 and now all works very well. I have my vue GUI opened on localhost 8000.

Unable to Run Puppeteer on AWS lambda

I am trying to run a small script in AWS lambda using AWSCloud9 but always get an error...!
2020-04-06 20:21:45.163 Error: Failed to launch the browser process!
/var/task/node_modules/puppeteer/.local-chromium/linux-722234/chrome-linux/chrome: error while
loading shared libraries: libX11.so.6: cannot open shared object file: No such file or directory
TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/master/docs/troubleshooting.md
at onClose (/var/task/node_modules/puppeteer/lib/Launcher.js:750:14)
at Interface.<anonymous> (/var/task/node_modules/puppeteer/lib/Launcher.js:739:50)
at Interface.emit (events.js:323:22)
at Interface.close (readline.js:409:8)
at Socket.onend (readline.js:187:10)
at Socket.emit (events.js:323:22)
at endReadableNT (_stream_readable.js:1204:12)
at processTicksAndRejections (internal/process/task_queues.js:84:21)
Any Help??

Loopback lb-services.js Docular Error: Error: EPERM: operation not permitted,

I´m trying to generate the docs for the lb-services.js file of the Loopback Angular SDK. Howerver I´m getting this weird error when running grunt.
Running "docular" task
(node:18260) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
(node:18260) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
Loading individual files for gid: Base
Loading individual files for gid: loopback
Loading individual files for gid: lbServices
Parsing files for gid: Base
Parsing files for gid: loopback
Parsing files for gid: lbServices
Backfilling file data for gid: Base
Backfilling file data for gid: loopback
Backfilling file data for gid: lbServices
Creating docs from for gid: Base
Creating docs from for gid: loopback
Creating docs from for gid: lbServices
Error: EPERM: operation not permitted, open 'docular_generated\sources\lb-services.js'
at Error (native)
at Object.fs.openSync (fs.js:634:18)
at copyFileSync (node_modules\fs-extra\lib\copy-sync\copy-file-sync.js:21:16)
at Object.copySync (node_modules\fs-extra\lib\copy-sync\copy-sync.js:32:7)
at .<anonymous> (node_modules\docular\lib\scripts\core\generator.js:132:25)
at _combinedTickCallback (internal/process/next_tick.js:67:7)
at process._tickDomainCallback (internal/process/next_tick.js:122:9)
at process.fallback (C:\Users\pablo\Dropbox\Nozzmo\Reuniones\exeboard\backend\node_modules\async-listener\index.js:450:15)
From previous event:
at Group.extend.exportDocFiles (node_modules\docular\lib\scripts\core\generator.js:123:25)
at _combinedTickCallback (internal/process/next_tick.js:67:7)
at process._tickDomainCallback (internal/process/next_tick.js:122:9)
at process.fallback (node_modules\async-listener\index.js:450:15)
{ Error: EPERM: operation not permitted, open 'docular_generated\sources\lb-services.js'
at Error (native)
at Object.fs.openSync (fs.js:634:18)
at copyFileSync (node_modules\fs-extra\lib\copy-sync\copy-file-sync.js:21:16)
at Object.copySync (node_modules\fs-extra\lib\copy-sync\copy-sync.js:32:7)
at .<anonymous> (node_modules\docular\lib\scripts\core\generator.js:132:25)
at _combinedTickCallback (internal/process/next_tick.js:67:7)
at process._tickDomainCallback (internal/process/next_tick.js:122:9)
at process.fallback (node_modules\async-listener\index.js:450:15)
From previous event:
at Group.extend.exportDocFiles (node_modules\docular\lib\scripts\core\generator.js:123:25)
at _combinedTickCallback (internal/process/next_tick.js:67:7)
at process._tickDomainCallback (internal/process/next_tick.js:122:9)
at process.fallback (node_modules\async-listener\index.js:450:15)
errno: -4048,
code: 'EPERM',
syscall: 'open',
path: 'docular_generated\\sources\\lb-services.js' }
Warning: Task "docular" failed. Use --force to continue.
Aborted due to warnings.
I´m using Windows 10 and Node v6.0.0. The gruntfile just contains the
'loopback_sdk_angular', 'docular',
'uglify'
taks.
Can anyone help me find the cause of this error?

Error: failed to connect to [localhost:27017]

When I run node app.js, I get the following error:
Failed to load c++ bson extension, using pure JS version
Express server listening on port 3000
events.js:85
throw er; // Unhandled 'error' event
^
Error: failed to connect to [localhost:27017]
at null.<anonymous> (/Users/me/development/node_modules/mongodb/lib/mongodb/connection/server.js:553:74)
at emit (events.js:118:17)
at null.<anonymous> (/Users/me/development/node_modules/mongodb/lib/mongodb/connection/connection_pool.js:140:15)
at emit (events.js:110:17)
at Socket.<anonymous> (/Users/me/developmen/node_modules/mongodb/lib/mongodb/connection/connection.js:512:10)
at Socket.emit (events.js:107:17)
at net.js:451:14
at process._tickCallback (node.js:355:11)
I'm not sure whether this is localhost problem or an issue with the connection to mongodb. I tried looking at similar questions SO and Github but it didn't help me.

Seems like mongodb server is not running. Check it