Yeoman angular build process issue - gruntjs

I am getting this error which I am unable to interprete correctly.
Can somebody give me a good hint.
Thanks a lot
Peter
Warning: Running "imagemin:dist" (imagemin) task
Fatal error: Cannot read property 'contents' of undefined
Execution Time (2015-11-29 16:40:32 UTC)
loading tasks 387ms ▇▇▇▇ 12%
loading grunt-contrib-imagemin 2.6s ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 79%
imagemin:dist 288ms ▇▇▇ 9%
Total 3.3s Used --force, continuing.
Running "imagemin:dist" (imagemin) task
Fatal error: Cannot read property 'contents' of undefined

I had a similar error.
In my case it helped doing:
sudo npm cache clean && npm install grunt-contrib-imagemin

Try updating "grunt-contrib-imagemin": "^1.0.0" in your package.json.
More info here: https://github.com/gruntjs/grunt-contrib-imagemin/issues/325

Related

after installing image crop picker and debug problem

my all project is working fine but when i install image crop picker dependency then it shows the error even there is no build.
FAILURE: Build failed with an exception. Error given below
What went wrong:
Execution failed for task ':app:processDebugResources'.
A failure occurred while executing com.android.build.gradle.internal.tasks.Workers$ActionFacade
Android resource linking failed
F:\bgbyteappfolder\newbgb\node_modules\react-native-image-crop-picker\android\build\intermediates\library_manifest\debug\AndroidManifest.xml:10:5-14:15: AAPT: error: unexpected element found in .
BUILD FAILED in 31s
error Failed to install the app. Make sure you have the Android development environment set up: https://reactnative.dev/docs/environment-setup. Run CLI with --verbose flag for more details.
Error: Command failed: gradlew.bat app:installDebug -PreactNativeDevServerPort=8081
Note: Some input files use or override a deprecated API..
i Am expecting rapid action on this failure stackoverflow family
Upgrade your gradle version by adding classpath 'com.android.tools.build:gradle:4.0.1' in your android/build.gradle file:
buildscript {
dependencies {
classpath 'com.android.tools.build:gradle:4.0.1'
}
}
After this clean your build folder by:
cd android
./gradlew clean

Sails grunt watch - Warning: Cannot read property 'bigint' of undefined Use --force to continue

I run sails on current project, just copied current project to new macbook high sierra and suddenly shown this error when running task grunt and edit asset files.
Sails version: 1.0.2
Grunt-cli version: 1.2.0
Grunt version: 1.0.3
Npm vesion: 6.1.0
Running "watch" task
Waiting...
>> File "assets/styles/project/_colors.scss" changed.
Running "less:dev" (less) task
>> 1 stylesheet created.
Running "sass:dev" (sass) task
Running "sync:dev" (sync) task
**Warning: Cannot read property 'bigint' of undefined Use --force to continue.**
When i run trace for this problem will show this
Warning: Cannot read property 'bigint' of undefined Use --force to continue.
TypeError: Cannot read property 'bigint' of undefined
at Object.stat (fs.js:795:37)
at Object.stat (/Users/erwinsetiawan/Works/Project/review-portal/node_modules/sails-hook-grunt/node_modules/promised-io/promise.js:709:17)
at processPair (/Users/erwinsetiawan/Works/Project/review-portal/node_modules/sails-hook-grunt/node_modules/grunt-sync/tasks/sync.js:143:28)
at /Users/erwinsetiawan/Works/Project/review-portal/node_modules/sails-hook-grunt/node_modules/grunt-sync/tasks/sync.js:52:16
at Array.map (<anonymous>:null:null)
at Object.<anonymous> (/Users/erwinsetiawan/Works/Project/review-portal/node_modules/sails-hook-grunt/node_modules/grunt-sync/tasks/sync.js:37:38)
at Array.map (<anonymous>:null:null)
at Object.<anonymous> (/Users/erwinsetiawan/Works/Project/review-portal/node_modules/sails-hook-grunt/node_modules/grunt-sync/tasks/sync.js:29:28)
at Object.<anonymous> (/Users/erwinsetiawan/Works/Project/review-portal/node_modules/grunt/lib/grunt/task.js:252:15)
at Object.thisTask.fn (/Users/erwinsetiawan/Works/Project/review-portal/node_modules/grunt/lib/grunt/task.js:70:16)
at Object.<anonymous> (/Users/erwinsetiawan/Works/Project/review-portal/node_modules/grunt/lib/util/task.js:294:30)
at Task.runTaskFn (/Users/erwinsetiawan/Works/Project/review-portal/node_modules/grunt/lib/util/task.js:244:24)
at Task.<anonymous> (/Users/erwinsetiawan/Works/Project/review-portal/node_modules/grunt/lib/util/task.js:293:12)
at /Users/erwinsetiawan/Works/Project/review-portal/node_modules/grunt/lib/util/task.js:220:11
at process._tickCallback (internal/process/next_tick.js:61:11)
It nothing happen when run this project to another laptop old el capitan and windows
Anyone can help me to solve di problem?
This appears to be fixed in grunt-sync 0.8.0. I suggest updating the grunt-sync package.
This is now fixed in sails-hook-grunt#4.0.1 (see https://github.com/balderdashy/sails/issues/4470 for more information)
Downgrade from node 10.5.0 to node 10.4.1 fix this problem, so probably current grunt version not yet supported the newest node version.

Why does grunt.loadNpmTask('grunt-contrib-jshint') trigger an error in Sails.js?

This seems pretty straightforward, but I can't seem to debug this error. I've added this code to my Sails API as /tasks/config/jshint.js
module.exports = function(grunt) {
console.log(1);
grunt.config.set('jshint', {
files: {
src: ['api/services/*.js', 'api/policies/*.js', 'api/controllers/*.js']
}
});
console.log(2);
grunt.loadNpmTask('grunt-contrib-jshint');
console.log(3);
};
Now, when I execute any grunt task, I get an error message (but the older tasks still execute successfully).
C:\dev\fo-rest-api>grunt aglio
1
2
Loading "Gruntfile.js" tasks...ERROR
>> TypeError: undefined is not a function
Running "aglio:your_target" (aglio) task
...
Done, without errors.
When I run the jshint task, I get the same loading error and the task is aborted.
C:\dev\fo-rest-api>grunt jshint
1
2
Loading "Gruntfile.js" tasks...ERROR
>> TypeError: undefined is not a function
Warning: Task "jshint" not found. Use --force to continue.
Aborted due to warnings.
C:\dev\fo-rest-api>
A few other notes:
Using --force only changes the wording of the error message.
grunt-contrib-jshint seems to be successfully installed in /node_modules (I deleted everything and re-ran npm install to be sure.
I'm running this on Windows, if that matters. I've tried opening the command line as both a normal user and as administrator.
I tried commenting out the loadNpmTask line to see if sails would load it automatically, but still got Warning: Task "jshint" not found.
Thanks for any clues you might have.
The answer was pretty straightforward. I somehow deleted the s at the end of grunt.loadNpmTasks. When I added it back, everything worked well.
I wish there was some sort of syntax highlighting that for common packages like grunt that would identify this kind of typo...

After Yeoman scaffolding, "grunt serve" not working

I followed the Yeoman tutorial to the T yet it doesn't work for me.
I'm getting this error:
C:\Users\Imray\Projects\myProj\v2>grunt serve
Loading "imagemin.js" tasks...ERROR
>> Error: Cannot find module 'rimraf'
Loading "watch.js" tasks...ERROR
>> Error: Cannot find module 'lodash'
Running "serve" task
Warning: Task "watch" not found. Use --force to continue.
Aborted due to warnings.
Execution Time (2014-12-14 15:38:18 UTC)
loading tasks 9ms ■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■ 45%
serve 9ms ■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■ 45%
Total 20ms
Any ideas why I am getting this error and how to overcome it?
Looks like you do not have the dependencies properly installed.
Do a npm install and bower install, after successfull completion try grunt serve again.

Grunt-karma aborted due to warnings

I'm getting "Aborted due to warnings" error when running grunt in --verbose mode.
ar#Woody:~/www/mysite-frontend-dev$ grunt build:debug
...
Registering "grunt-karma" local Npm module tasks.
Reading /home/ar/www/mysite-frontend-dev/node_modules/grunt-karma/package.json...OK
Parsing /home/ar/www/mysite-frontend-dev/node_modules/grunt-karma/package.json...OK Use --force to continue.
Aborted due to warnings.
Is there a way to get more detailed output? This warning message doesn't say much...
In general you can pass a command-line flag like $ grunt build:debug --verbose or $ grunt build:debug --stack to see more details
There was an issue with grunt-concurrent and Debian "squeeze". Updating to the latest (0.4.1) grunt-concurrent resolved the problem.

Resources