laravel-elixir - elixir.config.js not defined - laravel-elixir

I'm trying to add the reactify transformer to browserfy:
var elixir = require('laravel-elixir');
elixir.config.js.browserify.transformers.push({
name: 'reactify',
options: {}
});
elixir(function(mix) {
mix.sass('app.scss');
mix.browserify('App.js');
});
and I get this error:
TypeError: Cannot read property 'browserify' of undefined
at Object.<anonymous> (/Users/carlo/Dev/jscomix/gulpfile.js:15:17)
at Module._compile (module.js:460:26)
at Object.Module._extensions..js (module.js:478:10)
at Module.load (module.js:355:32)
at Function.Module._load (module.js:310:12)
at Module.require (module.js:365:17)
at require (module.js:384:17)
at Liftoff.handleArguments (/usr/local/lib/node_modules/gulp/bin/gulp.js:116:3)
at Liftoff.<anonymous> (/usr/local/lib/node_modules/gulp/node_modules/liftoff/index.js:192:16)
at module.exports (/usr/local/lib/node_modules/gulp/node_modules/liftoff/node_modules/flagged-respawn/index.js:17:3)
Seems that the config variable is not set. Can anyone see anything wrong in the code?

For anyone having this problem, the issue was an old elixir version (2.0.0), it's working properly in version 3.0.0

Related

Forge app for Jira can’t run because ‘experiment is not enabled’

I am a very beginner in Forge and JS, trying to run my app but can’t do because of that error:
File was processed with these loaders:
* ../tunnel/node_modules/babel-loader/lib/index.js
You may need an additional loader to handle the result of these loaders.
Error: The top-level-await experiment is not enabled (set experiments.topLevelAwait: true to enabled it)
at /tunnel/node_modules/webpack/lib/dependencies/HarmonyDetectionParserPlugin.js:54:11
at Hook.eval [as call] (eval at create (/tunnel/node_modules/tapable/lib/HookCodeFactory.js:19:10), <anonymous>:7:16)
at Hook.CALL_DELEGATE [as _call] (/tunnel/node_modules/tapable/lib/Hook.js:14:14)
at JavascriptParser.walkAwaitExpression (/tunnel/node_modules/webpack/lib/javascript/JavascriptParser.js:2314:29)
at JavascriptParser.walkExpression (/tunnel/node_modules/webpack/lib/javascript/JavascriptParser.js:2244:10)
at JavascriptParser.walkVariableDeclaration (/tunnel/node_modules/webpack/lib/javascript/JavascriptParser.js:2098:33)
at JavascriptParser.walkStatement (/tunnel/node_modules/webpack/lib/javascript/JavascriptParser.js:1592:10)
at JavascriptParser.walkStatements (/tunnel/node_modules/webpack/lib/javascript/JavascriptParser.js:1453:9)
at JavascriptParser.parse (/tunnel/node_modules/webpack/lib/javascript/JavascriptParser.js:3338:9)
at /tunnel/node_modules/webpack/lib/NormalModule.js:1080:26
at processResult (/tunnel/node_modules/webpack/lib/NormalModule.js:793:11)
at /tunnel/node_modules/webpack/lib/NormalModule.js:853:5
at /tunnel/node_modules/loader-runner/lib/LoaderRunner.js:406:3
at iterateNormalLoaders (/tunnel/node_modules/loader-runner/lib/LoaderRunner.js:232:10)
at iterateNormalLoaders (/tunnel/node_modules/loader-runner/lib/LoaderRunner.js:239:10)
at /tunnel/node_modules/loader-runner/lib/LoaderRunner.js:254:3`
I already found it’s needed to put this excerpt to webpack.config.js file
experiments: {
topLevelAwait: true
}
However, I can’t find this file.
What to do to make the app running?

How do I stop this error from returning after running Lando start or rebuild on a drupal template project

I get this error everytime I run lando start or lando rebuild on a project I've installed from a drupal 8 template.
I've redone composer create project, composer install, lando destroy, lando rebuild etc. None have worked. I've also checked to see if I have the most recent versions of lando, composer, & docker. So I'm not sure if this is an issue with something in the code or something else entirely.
OCI runtime exec failed: exec failed: container_linux.go:345: starting container process caused "exec: \"cd\": executable file not found in $PATH": unknown
error: Looks like one of your build steps failed! with Error
at module.exports.sh.Promise.try.then (/snapshot/lando/build/cli/lib/shell.js:0:0)
From previous event:
at Shell.sh (/snapshot/lando/build/cli/lib/shell.js:0:0)
at Object.exports.dc (/snapshot/lando/build/cli/lib/bootstrap.js:0:0)
at compose (/snapshot/lando/build/cli/lib/bootstrap.js:0:0)
at exports.run.Promise.each.docker.isRunning.then.then (/snapshot/lando/build/cli/lib/router.js:0:0)
From previous event:
at exports.run.Promise.each.datum (/snapshot/lando/build/cli/lib/router.js:0:0)
at runCallback (timers.js:696:18)
at tryOnImmediate (timers.js:667:5)
at processImmediate (timers.js:649:5)
From previous event:
at Object.exports.run (/snapshot/lando/build/cli/lib/router.js:0:0)
at run (/snapshot/lando/build/cli/lib/engine.js:0:0)
at exports.eventWrapper.daemon.up.then.then (/snapshot/lando/build/cli/lib/router.js:0:0)
From previous event:
at Object.exports.eventWrapper (/snapshot/lando/build/cli/lib/router.js:0:0)
at Engine.module.exports.constructor.engineCmd (/snapshot/lando/build/cli/lib/engine.js:0:0)
at Engine.run (/snapshot/lando/build/cli/lib/engine.js:0:0)
at Object.exports.runBuild (/snapshot/lando/build/cli/plugins/lando-services/lib/utils.js:0:0)
at AsyncEvents.module.exports.app.events.on.app.events.on (/snapshot/lando/build/cli/plugins/lando-services/app.js:0:0)
at AsyncEvents.handle (/snapshot/lando/build/cli/lib/events.js:0:0)
at emit.Promise.each.fn (/snapshot/lando/build/cli/lib/events.js:0:0)
From previous event:
at AsyncEvents.emit (/snapshot/lando/build/cli/lib/events.js:0:0)
at module.exports.start.initAndReport.then.then.then (/snapshot/lando/build/cli/lib/app.js:0:0)
From previous event:
at App.start (/snapshot/lando/build/cli/lib/app.js:0:0)
at Object.exports.appToggle (/snapshot/lando/build/cli/plugins/lando-core/lib/utils.js:0:0)
at Object.run (/snapshot/lando/build/cli/plugins/lando-core/tasks/start.js:0:0)
at module.exports.parseToYargs.checkForUpdates.then.lando.bootstrap.then.lando.events.emit.then.then.then.then.then (/snapshot/lando/build/cli/lib/cli.js:0:0)
From previous event:
at module.exports.parseToYargs.checkForUpdates.then.lando.bootstrap.then.lando (/snapshot/lando/build/cli/lib/cli.js:0:0)
From previous event:
at module.exports.parseToYargs.checkForUpdates.then (/snapshot/lando/build/cli/lib/cli.js:0:0)
at runCallback (timers.js:696:18)
at tryOnImmediate (timers.js:667:5)
at processImmediate (timers.js:649:5)
From previous event:
at Object.handler (/snapshot/lando/build/cli/lib/cli.js:0:0)
at Object.runCommand (/snapshot/lando/build/cli/node_modules/yargs/lib/command.js:238:44)
at Object.parseArgs [as _parseArgs] (/snapshot/lando/build/cli/node_modules/yargs/yargs.js:1063:30)
at Function.get [as argv] (/snapshot/lando/build/cli/node_modules/yargs/yargs.js:1004:21)
at Cli.run (/snapshot/lando/build/cli/lib/cli.js:0:0)
at lando.bootstrap.then.lando.getApp.init.then (/snapshot/lando/build/cli/bin/lando.js:0:0)
From previous event:
at lando.bootstrap.then.lando (/snapshot/lando/build/cli/bin/lando.js:0:0)
at runCallback (timers.js:696:18)
at tryOnImmediate (timers.js:667:5)
at processImmediate (timers.js:649:5)
From previous event:
at Object.<anonymous> (/snapshot/lando/build/cli/bin/lando.js:0:0)
at Module._compile (pkg/prelude/bootstrap.js:1254:22)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:711:10)
at Module.load (internal/modules/cjs/loader.js:610:32)
at tryModuleLoad (internal/modules/cjs/loader.js:549:12)
at Function.Module._load (internal/modules/cjs/loader.js:541:3)
at Function.Module.runMain (pkg/prelude/bootstrap.js:1309:12)
at startup (internal/bootstrap/node.js:274:19)
at bootstrapNodeJSCore (internal/bootstrap/node.js:608:3)
warn: This **MAY** prevent your app from working
warn: Check for errors above, fix them, and try again
I receive working urls despite this error.
edit: added docker-compose.yml file ...
version: '2'
services:
solr:
image: solr:8.1
ports:
- "8983:8983"
volumes:
- data:/opt/solr/server/solr/d8
- ./tests/solr-conf/8.x:/solr-conf/conf
entrypoint:
- docker-entrypoint.sh
- solr-precreate
- d8
- /solr-conf
volumes:
data:
Looks Ok to me:
$ docker-compose up
Creating network "stackoverflow-57693461_default" with the default driver
Creating volume "stackoverflow-57693461_data" with default driver
Pulling solr (solr:8.1)...
8.1: Pulling from library/solr
9cc2ad81d40d: Pull complete
(...)
f059ff7111be: Pull complete
Digest: sha256:6731556f68c4b8df2b1681f5a021014e9e1378c8a658ff90aa41a5071223e743
Status: Downloaded newer image for solr:8.1
Creating stackoverflow-57693461_solr_1 ... done
Attaching to stackoverflow-57693461_solr_1
solr_1 | Executing /opt/docker-solr/scripts/solr-precreate d8 /solr-conf
solr_1 | Executing /opt/docker-solr/scripts/precreate-core d8 /solr-conf
solr_1 | Created d8
solr_1 | Starting Solr 8.1.1
solr_1 | OpenJDK 64-Bit Server VM warning: Failed to reserve shared memory. (error = 1)
solr_1 | OpenJDK 64-Bit Server VM warning: Failed to reserve shared memory. (error = 1)
solr_1 | OpenJDK 64-Bit Server VM warning: Failed to reserve shared memory. (error = 1)
solr_1 | 2019-08-30 19:28:43.820 INFO (main) [ ] o.e.j.u.log Logging initialized #912ms to org.eclipse.jetty.util.log.Slf4jLog
(...)
solr_1 | 2019-08-30 19:28:45.789 INFO (main) [ ] o.e.j.s.AbstractConnector Started ServerConnector#1937eaff{HTTP/1.1,[http/1.1, h2c]}{0.0.0.0:8983}
solr_1 | 2019-08-30 19:28:45.789 INFO (main) [ ] o.e.j.s.Server Started #2883ms
How are you executing the container? through lando start, I presume ? I wonder what is in docker.yaml. This docker-compose.yaml is straight-forward. I don'
t see any issue with it.

Yeoman yo conmand

I am trying to use yeoman.
I have not found anyone who has had this particular error.
So far I have successfully installed Yeoman. When I run the yo command I get the following error:
/usr/local/lib/node_modules/yo/node_modules/fast-glob/out/providers/reader-sync.js:45
throw err;
^
Error: EACCES: permission denied, scandir '/usr/sbin/authserver'
at Object.fs.readdirSync (fs.js:875:3)
at exports.readdir (/usr/local/lib/node_modules/yo/node_modules/#mrmlnc/readdir-enhanced/lib/sync/fs.js:18:20)
at Object.safeCall [as safe] (/usr/local/lib/node_modules/yo/node_modules/#mrmlnc/readdir-enhanced/lib/call.js:24:8)
at DirectoryReader.readNextDirectory (/usr/local/lib/node_modules/yo/node_modules/#mrmlnc/readdir-enhanced/lib/directory-reader.js:78:10)
at Readable.DirectoryReader.stream._read (/usr/local/lib/node_modules/yo/node_modules/#mrmlnc/readdir-enhanced/lib/directory-reader.js:57:18)
at Readable.read (_stream_readable.js:455:10)
at readdirSync (/usr/local/lib/node_modules/yo/node_modules/#mrmlnc/readdir-enhanced/lib/sync/index.js:27:21)
at Function.readdirSyncStat (/usr/local/lib/node_modules/yo/node_modules/#mrmlnc/readdir-enhanced/lib/index.js:34:10)
at ReaderSync.dynamicApi (/usr/local/lib/node_modules/yo/node_modules/fast-glob/out/providers/reader-sync.js:61:24)
at ReaderSync.api (/usr/local/lib/node_modules/yo/node_modules/fast-glob/out/providers/reader-sync.js:53:25)
Emitted 'error' event at:
at DirectoryReader.emit (/usr/local/lib/node_modules/yo/node_modules/#mrmlnc/readdir-enhanced/lib/directory-reader.js:365:14)
at call.safe (/usr/local/lib/node_modules/yo/node_modules/#mrmlnc/readdir-enhanced/lib/directory-reader.js:81:14)
at onceWrapper (/usr/local/lib/node_modules/yo/node_modules/#mrmlnc/readdir-enhanced/lib/call.js:45:17)
at onceWrapper (/usr/local/lib/node_modules/yo/node_modules/#mrmlnc/readdir-enhanced/lib/call.js:45:17)
at exports.readdir (/usr/local/lib/node_modules/yo/node_modules/#mrmlnc/readdir-enhanced/lib/sync/fs.js:22:5)
at Object.safeCall [as safe] (/usr/local/lib/node_modules/yo/node_modules/#mrmlnc/readdir-enhanced/lib/call.js:24:8)
[... lines matching original stack trace ...]
at readdirSync (/usr/local/lib/node_modules/yo/node_modules/#mrmlnc/readdir-enhanced/lib/sync/index.js:27:21)

Not able to install loader in Webpacker

I'm trying to follow a getting started guide, of installing a npm package called Vux. It's basically a UI written in Vue.js. The guide says that i need to modify a Webpack config file to include vux loader. Everything looks pretty straight-forward, my config file should looke like that:
const vuxLoader = require('vux-loader')
const webpackConfig = originalConfig
module.exports = vuxLoader.merge(webpackConfig, {
plugins: ['vux-ui']
})
I have a plain Webpacker config file generated by Rails/Webpacker and, after following a doc, it looks like that:
# config/webpack/environment.js
const { environment } = require('#rails/webpacker')
const vuxLoader = require('vux-loader')
module.exports = vuxLoader.merge(environment, {
plugins: ['vux-ui']
})
You can see that file on git hub here
However, after that change, Webpack throws:
/Volumes/SUPPORT/Workspace/Personal/hcpl/node_modules/vux-loader/src/index.js:285
config.plugins.push(new webpack.LoaderOptionsPlugin({
^
TypeError: config.plugins.push is not a function
at Function.module.exports.merge (/Volumes/SUPPORT/Workspace/Personal/hcpl/node_modules/vux-loader/src/index.js:285:20)
at Object.<anonymous> (/Volumes/SUPPORT/Workspace/Personal/hcpl/config/webpack/environment.js:7:28)
at Module._compile (module.js:641:30)
at Object.Module._extensions..js (module.js:652:10)
at Module.load (module.js:560:32)
at tryModuleLoad (module.js:503:12)
at Function.Module._load (module.js:495:3)
at Module.require (module.js:585:17)
at require (internal/module.js:11:18)
at Object.<anonymous> (/Volumes/SUPPORT/Workspace/Personal/hcpl/config/webpack/development.js:1:83)
Does anyone have any idea what have i done wrong in here? I'm not too experienced with Webpack nor the Webpacker setup makes it even more complicated to find/test any solution from the internet.

Error: invalid bucket size spec: undefined

./zenbot.sh trade --manual
node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
In the future, you will have to enable it yourself.
See https://github.com/yagop/node-telegram-bot-api/issues/319. module.js:635:30
/home/local/zenbot/node_modules/timebucket/lib/bucket-size.js:15
if (!match) throw new Error('invalid bucket size spec: ' + spec);
^
Error: invalid bucket size spec: undefined
at BucketSize.parse (/home/local/zenbot/node_modules/timebucket/lib/bucket-size.js:15:21)
at new BucketSize (/home/local/zenbot/node_modules/timebucket/lib/bucket-size.js:5:21)
at Bucket.resize (/home/local/zenbot/node_modules/timebucket/lib/bucket.js:30:14)
at Command.<anonymous> (/home/local/zenbot/commands/trade.js:312:32)
at Command.listener (/home/local/zenbot/node_modules/commander/index.js:315:8)
at emitTwo (events.js:126:13)
at Command.emit (events.js:214:7)
at Command.parseArgs (/home/local/zenbot/node_modules/commander/index.js:653:12)
at Command.parse (/home/local/zenbot/node_modules/commander/index.js:475:21)
at /home/local/zenbot/zenbot.js:39:11
at /home/local/zenbot/boot.js:24:7
at f (/home/local/zenbot/node_modules/once/once.js:25:25)
at Glob.<anonymous> (/home/local/zenbot/node_modules/glob/glob.js:151:7)
at emitOne (events.js:116:13)
at Glob.emit (events.js:211:7)
at Glob._finish (/home/local/zenbot/node_modules/glob/glob.js:197:8)
at done (/home/local/zenbot/node_modules/glob/glob.js:182:14)
at Glob._processGlobStar2 (/home/local/zenbot/node_modules/glob/glob.js:637:12)
at /home/local/zenbot/node_modules/glob/glob.js:626:10
at RES (/home/local/zenbot/node_modules/inflight/inflight.js:31:16)
at f (/home/local/zenbot/nodemodules/once/once.js:25:25)
at lstatcb (/home/local/zenbot/node_modules/glob/glob.js:519:7)
I have no idea what could be causing this as I'm pretty sure I have followed the instructions to a T.
Trying to use this to manually trade on GDAX, i have my api keys on the conf.
I'm on windows 10 using "Bash on Ubuntu on Windows".
According to #938 issue on GitHub, this has been fixed in #926 and #940 pull requests.
So please consider upgrading your Zenbot. Otherwise raise a new issue.

Resources