I am using Jhiptser version 4.14.5, heroku version 7.19.3 and yarn 1.12.3
I upgraded my application from hipster 4.9.0 to 4.14.5 and am trying to deploy to heroku using command "jhipster heroku".
However am getting the following error. I have spent all day on this and not getting anywhere. Any help appreciated.
I cleaned and reinstalled node, yarn,jhipster and heroku , still same error.
I have cleaned yarn global cache as well.
Installing Heroku CLI deployment plugin
✖ { Error: Command failed: heroku plugins:install heroku-cli-deploy --force
Installing plugin java... yarn add v1.12.3
Installing plugin java... info No lockfile found.Installing plugin java... [1/4] Resolving packages...Installing plugin java... [2/4] Fetching packages...Installing plugin java... [3/4] Linking dependencies...Installing plugin java... [4/4] Building fresh packages...Installing plugin java... success Saved lockfile.Installing plugin java... success Saved 99 new dependencies.Installing plugin java... info Direct dependenciesInstalling plugin java... info All dependenciesInstalling plugin java... ├─ ansicolors#0.3.2Installing plugin java... ├─ co-wait#0.0.0Installing plugin java... ├─ color-name#1.1.3Installing plugin java... ├─ escape-string-regexp#1.0.5Installing plugin java... ├─ has-flag#3.0.0Installing plugin java... ├─ inherits#2.0.3Installing plugin java... ├─ isarray#1.0.0Installing plugin java... ├─ keyv#3.0.0Installing plugin java... ├─ ms#2.1.1Installing plugin java... ├─ opn#3.0.3Installing plugin java... ├─ pify#3.0.0Installing plugin java... ├─ safe-buffer#5.1.2Installing plugin java... ├─ sort-keys#2.0.0Installing plugin java... ├─ strip-ansi#4.0.0Installing plugin java... ├─ url-parse-lax#3.0.0Installing plugin java... └─ which#1.3.1Installing plugin java... Done in 4.45s.Installing plugin java... installed v3.0.1
Installing plugin --force... yarn add v1.12.3
Installing plugin --force... info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.Installing plugin --force... !
error Missing list of packages to add to your project.
Error: yarn add --force#latest --non-interactive --mutex=file:/Users/abhinav/.local/share/heroku/yarn.lock --preferred-cache-folder=/Users/abhinav/Library/Caches/heroku/yarn --check-files --registry=https://registry.npmjs.org exited with code 1
at ChildProcess.forked.on (/usr/local/Cellar/heroku/7.19.3/libexec/node_modules/#oclif/plugin-plugins/lib/yarn.js:31:28)
at ChildProcess.exithandler (child_process.js:294:12)
at ChildProcess.emit (events.js:182:13)
at maybeClose (internal/child_process.js:978:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:265:5)
killed: false,
code: 1,
signal: null,
cmd: 'heroku plugins:install heroku-cli-deploy --force' }
Related
So I don't know what's going with my computer, everyone I ask is saying this is strange and they never seen it before so I hoping someone here can help me before i just buy another computer lol...jk
This screenshot you see here is what happens after i run "npm create-react-app
idk why it just stays there and it only gives three files instead of giving me all the file i need for the react app (like public, SRC).
If someone sends me the folder with all the correct files Im able to run the react app and work on it, the issue is that Im not being able to create for some reason and my OCD is really killing me on this.
Please and thank you! :)
$ npx create-react-app myapp13
Creating a new React app in C:\Users\joesa\Desktop\myapp13.
Installing packages. This might take a couple of minutes.
Installing react, react-dom, and react-scripts with cra-template...
yarn add v1.22.4
[1/4] Resolving packages...
[2/4] Fetching packages...
info fsevents#1.2.12: The platform "win32" is incompatible with this module.
info "fsevents#1.2.12" is an optional dependency and failed compatibility check.
Excluding it from installation.
info fsevents#2.1.2: The platform "win32" is incompatible with this module.
info "fsevents#2.1.2" is an optional dependency and failed compatibility check.
Excluding it from installation.
[3/4] Linking dependencies...
warning "react-scripts > #typescript-eslint/eslint-plugin > tsutils#3.17.1" has unmet peer dependency "typescript#>=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta".
[4/4] Building fresh packages...
success Saved lockfile.
success Saved 14 new dependencies.
info Direct dependencies
├─ cra-template#1.0.3
├─ react-dom#16.13.1
├─ react-scripts#3.4.1
└─ react#16.13.1
info All dependencies
├─ #babel/plugin-syntax-typescript#7.10.1
├─ #babel/plugin-transform-flow-strip-types#7.9.0
├─ #babel/plugin-transform-runtime#7.9.0
├─ #babel/plugin-transform-typescript#7.10.1
├─ #babel/preset-typescript#7.9.0
├─ babel-preset-react-app#9.1.2
├─ cra-template#1.0.3
├─ eslint-config-react-app#5.2.1
├─ react-dev-utils#10.2.1
├─ react-dom#16.13.1
├─ react-error-overlay#6.0.7
├─ react-scripts#3.4.1
├─ react#16.13.1
└─ scheduler#0.19.1
Done in 12.46s.
Here you go: https://drive.google.com/drive/folders/1J-z39UQdqV5GP096TDs70m-WzJRiq_bY?usp=sharing
Make sure to run npm install
Try this:
npm uninstall -g create-react-app
npm install -g create-react-app#latest
npx create-react-app testApp
After npm install on clean environment, I get following problem with b package:
npm ls b
a#2.0.6
├── b#3.0.0
├─┬ c#3.0.1
│ └── UNMET DEPENDENCY b#^1.0.0
└─┬ d#4.1.1
└─┬ c#2.1.0
└── UNMET DEPENDENCY b#^1.0.0
npm ERR! missing: b#^1.0.0, required by c#3.0.1
npm ERR! missing: b#^1.0.0, required by c#2.1.0
This obviously causes errors, as package c needs b#^1.0.0, but receives b#3.0.0.
I struggled to force npm to install both versions as if they were different packages. Tried going through npm docs, package-locks, and shinkwrap, but with no success. How can I solve this problem?
Environment info:
OS: macOS High Sierra 10.13.4
npm: 6.10
node: v8.8.1
Playing around I noticed, that a lot of packages had UNMET DEPENDENCY. Following procedure fixed the problem:
rm -rf node_modules
npm cache clean --force
npm install
After cleaning npm cache the issue is completely resolved:
a#2.0.6
├── b#3.0.0
├─┬ c#3.0.1
│ └── b#^1.0.0
└─┬ d#4.1.1
└─┬ c#2.1.0
└── b#^1.0.0
Strange bug.
I am attempting to install Keystonejs following these instructions, but I am receiving a dependency error message when installing yo:
npm ERR! code ETARGET
npm ERR! notarget No matching version found for lodash#3.3.1
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
SPECS:
node v8.9.4
OS: macOS HighSierra V10.13.3
It appears that lodash#3.3.1 had an issue with the NPM register at the time, but this makes me wonder why this hasn't be upgraded within yo - which in turn makes me thing I am somehow screwing up the process.
Anyway anyone could point me in the right direction would be highly appreciated.
Mike
I don't have the answer, but I just thought I'd share with you:
My node is v7.10.1 and my npm is 4.2.0 and I can install lodash#3.3.1 without any problem:
me#computer:~/Downloads/lodash-test$ npm install lodash#3.3.1
/home/me/Downloads/lodash-test
└── lodash#3.3.1
Also I can install yo without any issue, and the its lodash dependencies have version 4.17.5:
me#computer:~/Downloads/lodash-test$ npm install yo
...
...
Yeoman Doctor
Running sanity checks on your system
✔ Global configuration file is valid
✔ NODE_PATH matches the npm root
✔ Node.js version
✔ No .bowerrc file in home directory
✔ No .yo-rc.json file in home directory
✔ npm version
Everything looks all right!
/home/me/Downloads/lodash-test
└─┬ yo#2.0.1
├─┬ async#2.6.0
│ └── lodash#4.17.5
...
...
├── lodash#4.17.5
├─┬ meow#3.7.0
│ ├─┬ camelcase-keys#2.1.0
...
...
I developed a web page with KeystoneJS a few months ago around December 2017. When I look at its package.json file, I see that the lodash version is 4.13.1:
...
"keystone": "4.0.0-beta.5",
"lodash": "^4.13.1",
...
I am having problem while using Yeoman, I have updated node to 6.2, but still having problem with generating scaffold. It seem that fsevents#1.0.12 is not compatible with my architecture. what can I do ?
This is the output
$ yo webapp
_-----_
| | .--------------------------.
|--(o)--| | 'Allo 'allo! Out of the |
`---------´ | box I include HTML5 |
( _´U`_ ) | Boilerplate, jQuery, and |
/___A___\ | a gulpfile to build your |
| ~ | | app. |
__'.___.'__ '--------------------------'
´ ` |° ´ Y `
? What more would you like? (Press <space> to select)Sass, Bootstrap, Modernizr
? Choose your style of DSL BDD
create bower.json
create package.json
create gulpfile.js
identical .babelrc
identical .gitignore
identical .gitattributes
identical .bowerrc
identical .editorconfig
create app/favicon.ico
create app/apple-touch-icon.png
create app/robots.txt
create app/styles/main.scss
create app/scripts/main.js
create app/index.html
create test/spec/test.js
create test/index.html
I'm all done. Running npm install & bower install for you to install the required dependencies. If this fails, try running the command yourself.
npm WARN deprecated graceful-fs#3.0.8: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs#^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN deprecated lodash#1.0.2: lodash#<3.0.0 is no longer maintained. Upgrade to lodash#^4.0.0.
npm WARN deprecated graceful-fs#1.2.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs#^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN deprecated cross-spawn-async#2.2.4: cross-spawn no longer requires a build toolchain, use it instead!
npm WARN deprecated graceful-fs#2.0.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs#^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN prefer global node-gyp#3.3.1 should be installed with -g
> node-sass#3.7.0 install /home/theo/Lin/webapp/node_modules/node-sass
> node scripts/install.js
Binary downloaded and installed at /home/theo/Lin/webapp/node_modules/node-sass/vendor/linux-x64-46/binding.node
> node-sass#3.7.0 postinstall /home/theo/Lin/webapp/node_modules/node-sass
> node scripts/build.js
"/home/theo/Lin/webapp/node_modules/node-sass/vendor/linux-x64-46/binding.node" exists.
testing binary.
Binary is fine; exiting.
> optipng-bin#3.1.2 postinstall /home/theo/Lin/webapp/node_modules/optipng-bin
> node lib/install.js
✔ optipng pre-build test passed successfully
> jpegtran-bin#3.0.6 postinstall /home/theo/Lin/webapp/node_modules/jpegtran-bin
> node lib/install.js
✔ jpegtran pre-build test passed successfully
> gifsicle#3.0.3 postinstall /home/theo/Lin/webapp/node_modules/gifsicle
> node lib/install.js
✔ gifsicle pre-build test passed successfully
/home/theo/Lin/webapp
├─┬ babel-core#6.9.0
│ ├─┬ babel-code-frame#6.8.0
│ │ ├── esutils#2.0.2
│ │ └── js-tokens#1.0.3
│ ├─┬ babel-generator#6.9.0
........................
........................
├── glob#4.5.3
├── lodash#2.4.2
├── propprop#0.3.0
└─┬ through2#0.6.5
└─┬ readable-stream#1.0.34
└── isarray#0.0.1
npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents#1.0.12
Fsevents is an optional dependency for Mac OSX. You don't need to worry about it.
https://www.npmjs.com/package/fsevents
I have an app written using Mean.IO and deployed to Heroku (Buildpack https://github.com/mbuchetics/heroku-buildpack-nodejs-grunt).
It's been fine up until my latest deploy this morning and has broken for no apparent reason. Bower seems to be running fine
2015-01-06T00:09:50.851963+00:00 app[web.1]: Error: ENOENT, no such file or directory '/app/bower_components/jquery/dist/jquery.min.map'
2015-01-06T00:09:50.851967+00:00 app[web.1]: at Object.fs.openSync (fs.js:439:18)
2015-01-06T00:09:50.851969+00:00 app[web.1]: at Object.fs.readFileSync (fs.js:290:15)
2015-01-06T00:09:50.851979+00:00 app[web.1]: at Promise.<anonymous> (/app/node_modules/mongoose/node_modules/mpromise/lib/promise.js:177:8)
2015-01-06T00:09:50.851984+00:00 app[web.1]: at Promise.fulfill (/app/node_modules/mongoose/node_modules/mpromise/lib/promise.js:97:20)
2015-01-06T00:09:50.851982+00:00 app[web.1]: at Promise.emit (/app/node_modules/mongoose/node_modules/mpromise/lib/promise.js:84:38)
2015-01-06T00:09:50.851985+00:00 app[web.1]: at Object.cb (/app/node_modules/mongoose/lib/query.js:1146:30)
2015-01-06T00:09:50.851981+00:00 app[web.1]: at Promise.emit (events.js:95:17)
2015-01-06T00:09:50.851976+00:00 app[web.1]: at Config.onPackageRead (/app/node_modules/meanio/lib/config.js:101:25)
2015-01-06T00:09:50.869507+00:00 app[web.1]: Worker 11 died :(
Relevant deploy code here
-----> Installing dependencies
npm WARN package.json karma-chrome-launcher#0.1.7 No README data
npm WARN package.json karma-coffee-preprocessor#0.2.1 No README data
npm WARN package.json karma-coverage#0.2.7 No README data
npm WARN package.json karma-phantomjs-launcher#0.1.4 No README data
> mean#0.4.2 postinstall /tmp/build_f7b66ed6667be26db9cf377edd6379ea
> node node_modules/meanio/node_modules/mean-cli/bin/mean-postinstall
Installing Bower dependencies
Auto installing package dependencies
Auto installing package dependencies
Installing module: mean-admin:
git clone --branch master https://git.mean.io/linnovate/mean-admin.git packages/contrib/mean-admin
Dependencies installed for package access
Dependencies installed for package articles
Dependencies installed for package system
Dependencies installed for package theme
Dependencies installed for package users
Dependencies installed for package dashboard
Dependencies installed for package linktexting
> mean-health#0.1.7 postinstall /tmp/build_f7b66ed6667be26db9cf377edd6379ea/packages/contrib/mean-admin/node_modules/mean-health
> node ./postinstall.js
Error: ENOENT, open '.bower-cache/fe2fe255e91d251051d543998aa8327a-1.11.2.lock'
gridfs-stream#0.5.3 node_modules/gridfs-stream
mean-health#0.1.7 node_modules/mean-health
request#2.51.0 node_modules/request
Dependencies installed for package mean-admin
-----> Caching node_modules directory for future builds
-----> Cleaning up node-gyp and npm artifacts
-----> Building runtime environment
-----> Exporting config vars to environment
grunt-cli#0.1.13 node_modules/grunt-cli
├── resolve#0.3.1
├── nopt#1.0.10 (abbrev#1.0.5)
└── findup-sync#0.1.3 (glob#3.2.11)
grunt#0.4.5 node_modules/grunt
-----> Found Gruntfile, running grunt heroku:development task
Running "cssmin:core" (cssmin) task
>> Destination not written because minified CSS was empty.
Running "uglify:core" (uglify) task
>> Destination bower_components/build/js/dist.min.js not written because src files were empty.
Done, without errors.
I see the line
Error: ENOENT, open '.bower-cache/fe2fe255e91d251051d543998aa8327a-1.11.2.lock'
But I'm not sure what that means heroku wise. Any ideas?
Try running bower update it will install the missing jQuery dependencies
From the documentation
http://learn.mean.io/#m-e-a-n-stack-more-information
**Update NPM, Bower or Grunt**
Sometimes you may find there is a weird error during install
like npm’s Error: ENOENT. Usually updating those tools to
the latest version solves the issue.
Updating NPM:
$ npm update -g npm
Updating Grunt:
$ npm update -g grunt-cli
Updating Bower:
$ npm update -g bower