I use Modulus.IO to deploy my Meteor app.
When I am on the development environment there is no problem at all, not in the 'meteor' console nor in the browser js console. But when I deploy it to Modulos.IO, this error appears in Modulus:
Error: Can't find npm module 'uglify-js'. Did you forget to call 'Npm.depends' in package.js within the 'minifiers' package?
at Object.Npm.require (/mnt/data/1/programs/server/boot.js:106:17)
at Package (packages/minifiers/minifiers.js:1)
at packages/minifiers.js:307:4
at packages/minifiers.js:317:3
at /mnt/data/1/programs/server/boot.js:155:10
at Array.forEach (native)
at Function._.each._.forEach (/mnt/data/1/node_modules/underscore/underscore.js:79:11)
at /mnt/data/1/programs/server/boot.js:82:5
[2014-05-16T11:48:10.665Z] Application CRASH detected. Exit code 8.
[2014-05-16T11:48:12.326Z] Application restarted.
/mnt/data/1/programs/server/boot.js:186
}).run();
I have no minifiers package installed and no underscore.js as well.
Ok, good news.
That was some error between NPM and Modulus module version.
I've uninstalled NPM, Modulus module and stopped the deploy environment.
Then installed the latest version of NPM and installed the latest version of Modulus module.
Finally, I've made the deploy again and it's everything ok.
Thanks for all the attention.
P.S.: Remember to install Modulus module globally (-g).
Related
I'm new to jhipster. I am on jhipster v7.8.1, i can generate an app using the cli questions but when i try importing a jdl file i got the following error:
**ERROR! Class constructor GAstVisitor cannot be invoked without 'new'
TypeError: Class constructor GAstVisitor cannot be invoked without 'new'
at new DslMethodsCollectorVisitor
This occurs due to a recent bug in the one of JHipster libraries. As a temporary solution you can go to the JHipster installed location and find it's package.json file and override the package causing this error as follows. Then run npm install again.
"overrides":{
"chevrotain#10.1.2": {
"#chevrotain/gast": "10.1.2"
}
}
This will prevent the JHipster using latest package of that.
I experienced the same error and managed to get the JDL file to run by using version 7.8.1
I followed the following steps to get this done;
uninstall the current version of jhipster that is causing issues for
my case this was 7.9.2 . use this command npm uninstall -g
generator-jhipster
Install version 7.8.1 using this command npm
install -g generator-jhipster#7.8.1
Attempt to run your JDL using
this command jhipster jdl jhipster-jdl.jdl
At this stage, your JDL
will be able to run
Hi I'm trying to run an application in vs code, when I hit on tns run I get this error "The current application is not compatible with NativeScript CLI 8.2.3.
Run 'ns migrate' to migrate your project to the latest NativeScript version.
Alternatively you may try running it with '--force' to skip this check.".
When I try to run ns migrate I also get this error "Error: spawn git ENOENT
at onErrorNT (node:internal/child_process:478:16)
at processTicksAndRejections (node:internal/process/task_queues:83:21)".
Note: I did installed NativeScript 8.2.3.
Please help.
Can anyone help me with this. Im using Mac. I cant find the location of the rulemanager. Please see error below
Lxxxxxxx:pmd-bin-6.34.0 xxxxxx$ sfdx scanner:run pmd --target /usr/src --category rulesets/java/quickstart.xml -f sarif
(node:17810) [editions-autoloader-none-broadened] Error Plugin: sfdx-cli: editions-autoloader-none-broadened: Unable to determine a suitable edition, even after broadening.
module: #oclif/config#1.17.0
task: runHook init
plugin: sfdx-cli
root: /Users/xxxxxxx/.local/share/sfdx/client/7.100.0-9d243d8
See more details with DEBUG=*
(Use node --trace-warnings ... to show where the warning was created)
ERROR running scanner:run: Attempted to resolve unregistered dependency token: "RuleManager"
Kieran, this is an issue that we just discovered. It is related to an incompatibility with the version of Node.js that is bundled with the Salesforce CLI and a library that is used by sfdx-scanner.
A temporary workaround can be found at https://github.com/forcedotcom/sfdx-scanner/issues/412
You will need to use the npm installation instead of the pkg installer since you are interested in the Sarif output. Sarif output was added in version 2.6.0. The issue affects versions 2.6.0-2.8.0 when using the pkg installer on a Mac.
We hope to have a fix rolled out in the next couple of days. I will post here when version 2.9 has been released. Sorry for any inconvenience.
Kieran, this issue has been fixed in version 2.9.1. You can upgrade by executing the following commands in your shell.
sfdx plugins:uninstall #salesforce/sfdx-scanner
sfdx plugins:install #salesforce/sfdx-scanner
I'm trying to build a simple web app using Yew, Diesel, and Postgres. When I run
wasm-pack build --target web --out-name wasm --out-dir ./static
I get the following error:
*rust-lld: error: unable to find library -lpq*
I'm on macOS Catalina. I installed Postgres through Homebrew. My libpq.dylib file is at /usr/local/lib.
These are the troubleshooting I've tried already:
Added /usr/local/lib to $PATH. My pg_config shows LIBDIR = /usr/local/lib.
Re-installed Postgres
Updated rustc -nightly
Ideas here are not helpful as well: How can I link a Rust Wasm application with libpq via wasm-pack?
Still it is not resolved. I'd be grateful for any suggestions.
Libpq does not support the wasm-web platform as far as I'm aware therefore there is no way to make this work. As already mentioned in the comments you probably want to use diesel in your backend code, not in the frontend.
I am trying to install GTK on my Mac (running Catalina) using vcpkg.
I get the following error message on running ./vcpkg install gtk
How can I fix this?
Error: Building package glib:x64-osx failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with .\vcpkg update, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: glib:x64-osx
Vcpkg version: 2019.09.12-unknownhash
Additionally, attach any relevant sections from the log files above.
EDIT
I used --keep-going while running the install command, and it installed all the packages that do not require glib to build.
I've added the log file outputs:
config-x64-osx-dbg-out.log
config-x64-osx-dbg-err.log
CMakeOutput.log