I am working on an Application developed in Asp.Net with Angular.
While running my project using inetmgr, My angular is not working.
Then I checked in Task runner, Then get following error.
cmd.exe /c grunt -b "D:\DevProjects\LogisticMonitor\trunk\CcxTLM.Web" --gruntfile "D:\DevProjects\LogisticMonitor\trunk\CcxTLM.Web\Gruntfile.js" default
Running "clean:files" (clean) task
Warning: Object object has no method 'pluck' Use --force to continue.
Process terminated with code 3.
Aborted due to warnings.
I changed latest versions of all dependies in package.json. Then Build the project.
It fixed for me.
Related
I'm getting a non fatal exception while running the dotnet sonarscanner utility to send data to our sonarqube instance.
During "dotnet sonarscanner end" command an exception is being thrown of "Failure during analysis, Node.js command to start eslint-bridge was: /usr/bin/node /builds/app-namespace/app-name/.sonarqube/out/.sonar/.sonartmp/eslint-bridge-bundle/node_modules/eslint-bridge/bin/server 44002
java.lang.IllegalStateException: Failed to start server (10s timeout)"
Im currently running the command in an alpine docker container with
node : v10.14.2
dotnetcore: 2.2.3
The node and npm commands are available from the path and I have also specified the sonar.nodejs.executable in the sonarqube xml config.
Additionally what is the node package used for relating to a dotnet project?
The content is still being deployed to our sonarqube instance but I would like to understand the cause of the exception.
For C#/VB.NET code, the code analysis takes place in the build step because the SonarC#/VB.NET rules are written as Roslyn rules.
However, for most other languages analysed by SonarQube/Cloud, the analysis takes place in the scanner end step. The scanner downloads the language plugins from the SonarQube/Cloud server and calls each one to give it the chance to analyse any files it can handle.
The SonarJS plugin works with ESLint which uses NodeJS i.e. the node package is being used to analyse JavaScript files.
I'm trying to run the "phpunit" command from Windows command line in my project folder and having the error message:
Uncaught TypeError: trim() expects parameter to be string, boolean given in phar://C:/bin/phpunit.phar/sebastian-environment/Console.php:115
For my project I used Symfony and the tests reside in the test\AppBundle\Controller directory.
PHPUnit version: 6.1.1
PHP version: 7.1
PHPUnit responds well to the "phpunit" (from outside my project dir) and "phpunit --version" commands so I suppose I installed it correctly.
Can anyone help what the problem is? Thanks.
UPDATE:
Re-installing phpunit 6.1.2 solved the problem!
I'm using travis to test my code. Recently the grunt tasks have started to fail without no change being made to anything involved with grunt. (The new commit which is tested contains just very minor changes in two PHP files.)
Here is the part of log from travis:
$ grunt build:app
Running "typings:default" (typings) task
Warning: Cannot find any-promise implementation nor global.Promise. You must install polyfill or call require("any-promise/register") with your preferred implementation, e.g. require("any-promise/register")("bluebird") on application load prior to any require("any-promise"). Use --force to continue.
Aborted due to warnings.
The command "grunt build:app" exited with 3.
I tried to search for that warning message but couldn't find anything useful.
One more thing: When I run grunt build:app locally on my pc it works just fine.
Thanks for your time :)
I had the same problem when I started using grunt-typings. Worked locally and didn't work on my CI server. Ended up fixing it by doing what the error message suggests:
npm install bluebird
npm install any-promise
In GruntFile.js:
require("any-promise/register")("bluebird");
Update your node.js version to >v0.12. To check your version of node.js use node -v. The documentation of any-promise explains:
Node.js versions prior to v0.12 may have contained buggy versions of the global Promise. For this reason, the global Promise is not loaded automatically for these old versions. If using any-promise in Node.js versions versions <= v0.12, the user should register a desired implementation.
I'm getting this error when I try typing $modulus deploy into terminal from my app directory:
Determining Meteor version...
Meteor version: 1.1.0.2
Bundling Meteor App...
undefined
[Error] Error: Command failed: /bin/sh -c cd /Users/xx/Projects/Project1 && meteor bundle --directory /Users/xx/Projects/Project1/.demeteorized
This command has been deprecated in favor of 'meteor build', which allows you
to build for multiple platforms and outputs a directory instead of a single
tarball. See 'meteor help build'for more information.
WARNING: The output directory is under your source tree.
Errors prevented bundling:
While building the application:
client/Project1.js:138:29: Unexpected token =
I get the same result with $demeteorizer. It worked on an old version of the app, then I added some features in new branch, merged, and now I'm getting this error.
Already tried:
sudo npm update -g modulus
Turns out it was an actual error in my code. I had an extra closing curly brace somewhere.
In webstorm, running grunt serve from the terminal works flawlessly and presents me with a webpage. However, when I make a configuration and run that, there's an error concerning SASS to CSS compilation:
Running "concurrent:server" (concurrent) task
Warning: Running "compass:server" (compass) task
Warning: You need to have Ruby and Compass installed and in your system PATH for this task to work. More info: https://github.com/gruntjs/grunt-contrib-compass Use --force to continue.
Aborted due to warnings.
which I do not understand, as I'm using the same settings (described here)
Seems WebStorm doesn't see your terminal environment when being started from shortcut. Pleasee try editing the launcher as suggested in https://devnet.jetbrains.com/message/5513463#5513463 - does it help?