In order to update all the meteor packages in my app, I feed in the command meteor update --all-packages. Many packages seem to now be updated to their latest versions, BUT now when I try to start my app using meteor --port 8000, the firing up of the app seems to stall in the Starting your app / process indefinitely ...meaning my app never actually fires up anymore!
Find below an image illustrating my experience:
Does anyone know why this is happening and perhaps provide a solution to the issue? Looking forward to your help!
Find below further details.
Following is the reaction after I fed in: meteor update --all-packages
Changes to your project's package version selections from updating the release:
accounts-base upgraded from 1.3.1 to 1.4.3
accounts-facebook upgraded from 1.2.1 to 1.3.2
accounts-google upgraded from 1.2.0 to 1.3.2
accounts-oauth upgraded from 1.1.15 to 1.1.16
accounts-password upgraded from 1.4.0 to 1.5.1
accounts-ui upgraded from 1.1.9 to 1.3.1
accounts-ui-unstyled upgraded from 1.2.1 to 1.4.1
allow-deny upgraded from 1.0.6 to 1.1.0
autoupdate upgraded from 1.3.12 to 1.5.0
babel-compiler* upgraded from 6.19.4 to 7.2.0
babel-runtime upgraded from 1.0.1 to 1.3.0
base64 upgraded from 1.0.10 to 1.0.11
binary-heap upgraded from 1.0.10 to 1.0.11
blaze upgraded from 2.3.2 to 2.3.3
boilerplate-generator upgraded from 1.1.1 to 1.6.0
caching-compiler upgraded from 1.1.9 to 1.2.0
callback-hook upgraded from 1.0.10 to 1.1.0
check upgraded from 1.2.5 to 1.3.1
coffeescript downgraded from 1.12.6_1 to 1.0.17
ddp upgraded from 1.3.0 to 1.4.0
ddp-client upgraded from 2.0.0 to 2.3.3
ddp-common upgraded from 1.2.9 to 1.4.0
ddp-server upgraded from 2.0.0 to 2.2.0
diff-sequence upgraded from 1.0.7 to 1.1.0
dynamic-import upgraded from 0.1.1 to 0.5.0
ecmascript upgraded from 0.8.2 to 0.12.0
ecmascript-runtime upgraded from 0.4.1 to 0.7.0
ecmascript-runtime-client upgraded from 0.4.3 to 0.8.0
ecmascript-runtime-server upgraded from 0.4.1 to 0.7.1
ejson upgraded from 1.0.13 to 1.1.0
es5-shim upgraded from 4.6.15 to 4.8.0
facebook-config-ui upgraded from 1.0.1 to 1.0.2
facebook-oauth upgraded from 1.3.2 to 1.5.0
fastclick removed from your project
fetch added, version 0.1.0
google-config-ui upgraded from 1.0.0 to 1.0.1
google-oauth upgraded from 1.2.5 to 1.2.6
http upgraded from 1.2.12 to 1.4.1
id-map upgraded from 1.0.9 to 1.1.0
inter-process-messaging added, version 0.1.0
less upgraded from 2.7.9 to 2.8.0
localstorage upgraded from 1.1.1 to 1.2.0
logging upgraded from 1.1.17 to 1.1.20
meteor upgraded from 1.7.0 to 1.9.2
meteor-base upgraded from 1.1.0 to 1.4.0
minifier-css upgraded from 1.2.16 to 1.4.0
minifier-js upgraded from 2.1.1 to 2.4.0
minimongo upgraded from 1.2.1 to 1.4.5
mobile-experience upgraded from 1.0.4 to 1.0.5
modern-browsers added, version 0.1.2
modules upgraded from 0.9.2 to 0.13.0
modules-runtime upgraded from 0.8.0 to 0.10.2
mongo upgraded from 1.1.22 to 1.6.0
mongo-decimal added, version 0.1.0
mongo-dev-server added, version 1.1.0
mongo-id upgraded from 1.0.6 to 1.0.7
npm-mongo* upgraded from 2.2.30 to 3.1.1
oauth upgraded from 1.1.13 to 1.2.3
oauth2 upgraded from 1.1.11 to 1.2.1
ordered-dict upgraded from 1.0.9 to 1.1.0
promise upgraded from 0.8.9 to 0.11.1
random upgraded from 1.0.10 to 1.1.0
rate-limit upgraded from 1.0.8 to 1.0.9
reactive-dict upgraded from 1.1.9 to 1.2.1
reload upgraded from 1.1.11 to 1.2.0
retry upgraded from 1.0.9 to 1.1.0
routepolicy upgraded from 1.0.12 to 1.1.0
session upgraded from 1.1.7 to 1.1.8
shell-server upgraded from 0.2.4 to 0.4.0
socket-stream-client added, version 0.2.2
srp upgraded from 1.0.10 to 1.0.12
standard-minifier-css upgraded from 1.3.4 to 1.5.0
standard-minifier-js upgraded from 2.1.1 to 2.4.0
tracker upgraded from 1.1.3 to 1.2.0
url upgraded from 1.1.0 to 1.2.0
webapp upgraded from 1.3.17 to 1.7.0
* These packages have been updated to new versions that are not backwards
compatible.
escrow: updated to Meteor 1.8.
-- Notice --
1.7: The underscore package has been removed as a dependency of all packages in
meteor-base. Since some apps may have been using underscore through this
dependency without having it listed in their .meteor/packages files, it
has been added automatically. If your app is not using underscore, then
you can safely remove it using 'meteor remove underscore'.
Changes to your project's package version selections from updating package
versions:
caching-html-compiler upgraded from 1.1.2 to 1.1.3
iron:url upgraded from 1.0.11 to 1.1.0
jquery upgraded from 1.11.10 to 1.11.11
mizzao:timesync upgraded from 0.3.4 to 0.5.0
momentjs:moment upgraded from 2.18.1 to 2.22.2
spacebars-compiler upgraded from 1.1.2 to 1.1.3
standard-minifier-css upgraded from 1.5.0 to 1.5.1
templating-compiler upgraded from 1.3.2 to 1.3.3
The following top-level dependencies were not updated to the very latest
version available:
* iron:router 1.1.1 (1.1.2 is available)
Newer versions of the following indirect dependencies are available:
* coffeescript 1.0.17 (2.3.1_2 is available)
These versions may not be compatible with your project.
To update one or more of these packages to their latest
compatible versions, pass their names to `meteor update`,
or just run `meteor update --all-packages`.
The package.json content is
{
'name': 'Mellrose',
'private': true,
'scripts': {
'start': 'meteor run'
},
'dependencies': {
'#babel/runtime': '^7.1.2',
'africastalking': '0.0.10',
'babel-runtime': '^6.20.0',
'bcrypt': '^1.0.3',
'meteor-node-stubs': '~0.2.4'
}
}
The current Meteor version is: Meteor 1.8
Ubuntu version is Ubuntu 16.04 LTS
Please help!
Related
When I deploy my .net core 2.1.0 project, I get the following error:
-----> Installing dotnet-framework 2.0.3
**ERROR** DEPENDENCY MISSING IN MANIFEST:
Version 2.0.3 of dependency dotnet-framework is not supported by this buildpack.
The versions of dotnet-framework supported in this buildpack are:
- 1.0.5
- 1.0.10
- 1.0.11
- 1.1.2
- 1.1.7
- 1.1.8
- 2.0.0
- 2.0.7
- 2.1.0
All solutions in my project is targeting the .net core framework 2.1.0, so I don't understand why this is.
I have dependencies in my project, and some of the them, like NETStandard.Library and Microsoft.NETCore.DotNetAppHost, are version 2.0.3, but does that really matter? (Also I don't think a version higher than 2.0.3 exist of NetStandard.Library.)
The project runs fine on my local machine, and ran fine on the host before we upgraded the buildpack and target .net framework, as well as various dependencies through NuGet.
Here is the full log:
https://1drv.ms/t/s!Ar81AKlFywcPhapTJdjZEnrcGrZS4A
You can try to pin the RuntimeFrameworkVersion to a specific one:
<RuntimeFrameworkVersion>2.0.7</RuntimeFrameworkVersion>
I faced below error when I ran below commands;
meteor update --patch
ran command meteor
ERROR
D:\test>meteor update --patch
Changes to your project's package version selections from updating the
release:
accounts-base upgraded from 1.2.17 to 1.3.0
babel-compiler upgraded from 6.18.2 to 6.19.1
boilerplate-generator upgraded from 1.0.11 to 1.1.0
dynamic-import added, version 0.1.0
ecmascript upgraded from 0.7.3 to 0.8.0
ecmascript-runtime upgraded from 0.3.15 to 0.4.1
ecmascript-runtime-client added, version 0.4.1
ecmascript-runtime-server added, version 0.4.1
localstorage upgraded from 1.0.12 to 1.1.0
meteor-base upgraded from 1.0.4 to 1.1.0
minifier-js upgraded from 2.0.0 to 2.1.0
minimongo upgraded from 1.0.23 to 1.2.0
modules upgraded from 0.8.2 to 0.9.0
modules-runtime upgraded from 0.7.10 to 0.8.0
mongo upgraded from 1.1.17 to 1.1.18
promise upgraded from 0.8.8 to 0.8.9
reactive-dict upgraded from 1.1.8 to 1.1.9
standard-minifier-js upgraded from 2.0.0 to 2.1.0
webapp upgraded from 1.3.15 to 1.3.16
test: updated to Meteor 1.4.4.3.
D:\test>meteor
[[[[[ ~\D\test ]]]]]
=> Started proxy.
=> Meteor 1.5 is available. Update this project with 'meteor update'.
=> Started MongoDB.
=> Errors prevented startup:
While selecting package versions:
error: Potentially incompatible change required to top-level
dependency: meteor-base 1.0.4, was 1.1.0.
Constraints on package "meteor-base":
* meteor-base#1.0.4 <- top level
* meteor-base#1.0.4 <- top level
Potentially incompatible change required to top-level dependency:
dynamic-import 0.1.0-beta.20, was 0.1.0.
Constraints on package "dynamic-import":
To allow potentially incompatible changes to top-level dependencies,
you must pass --allow-incompatible-update on the command line.
=> Your application has errors. Waiting for file change.
if you update to meteor 1.5 with meteor update Everything will work as expected with 0 conflict.
Dont touch any files!
Worked for me, first update that actually does not break anything.
I have noticed that the update included package "dynamic-import".
Just taking it out solved the issue. Then run with:
meteor --allow-incompatible-update
Maybe it is just a coincidence I have made this patch just a bit after the new Meteor 1.5 is launched. I wonder if this package should not be in this release.
So, ever since meteor unpinned package versions to the releases I've been experiencing this problem.
when I run $ meteor create [project], cd into that project and then check it with $ meteor update
I get the following:
$ meteor update
This project is already at Meteor 1.4.0.1, the latest release.
Your top-level dependencies are at their latest compatible versions.
Newer versions of the following indirect dependencies are available:
* autoupdate 1.2.11 (1.3.11 is available)
* caching-compiler 1.0.6 (1.1.6 is available)
* ddp-client 1.2.9 (1.3.0 is available)
* ddp-server 1.2.10 (1.3.9 is available)
* http 1.1.8 (1.2.8 is available)
* templating 1.1.14 (1.2.13 is available)
To update one or more of these packages, pass their names to `meteor
update`.
Which means then the next command is inevitably:
$ meteor update autoupdate caching-compiler ddp-client ddp-server http templating
Changes to your project's package version selections from updating package
versions:
autoupdate upgraded from 1.2.11 to 1.3.11
caching-compiler upgraded from 1.0.6 to 1.1.6
ddp-client upgraded from 1.2.9 to 1.3.0
ddp-server upgraded from 1.2.10 to 1.3.9
http upgraded from 1.1.8 to 1.2.8
templating upgraded from 1.1.14 to 1.2.13
And this is frankly annoying.
When I create a new project - I want everything to be the latest and greatest - new. Now, I understand sometimes some people don't want that and I'm okay with that. But for people like me, it sure would be nice to have a command meteor update everything - papa want's a brand new car!
Is anyone aware of such a command? The documentation doesn't seam to have this command listed.
Edit:
Note, that this also doesn't work:
$ meteor update --packages-only
Your top-level dependencies are at their latest compatible versions.
Newer versions of the following indirect dependencies are available:
* autoupdate 1.2.11 (1.3.11 is available)
* caching-compiler 1.0.6 (1.1.6 is available)
* ddp-client 1.2.9 (1.3.0 is available)
* ddp-server 1.2.10 (1.3.9 is available)
* http 1.1.8 (1.2.8 is available)
* templating 1.1.14 (1.2.13 is available)
To update one or more of these packages, pass their names to `meteor
update`.
Is Gracenote compatible with Windows 10 and Universal Windows Platform (UWP/UAP) ?
We were trying to install de Nuget Package from:
http://www.nuget.org/packages/ParkSquare.Gracenote/
and when we tried to install it, the Visual Studio 2015 throws in the output window:
===================================================
Restoring packages for 'MyApp.UWP'.
Restoring packages for C:\src\dev\MyApp.UWP\project.json...
Installing ParkSquare.Gracenote 1.3.0.
ParkSquare.Gracenote 1.3.0 is not compatible with UAP,Version=v10.0.
Some packages are not compatible with UAP,Version=v10.0.
ParkSquare.Gracenote 1.3.0 is not compatible with UAP,Version=v10.0 (win10-arm).
Some packages are not compatible with UAP,Version=v10.0 (win10-arm).
ParkSquare.Gracenote 1.3.0 is not compatible with UAP,Version=v10.0 (win10-arm-aot).
Some packages are not compatible with UAP,Version=v10.0 (win10-arm-aot).
ParkSquare.Gracenote 1.3.0 is not compatible with UAP,Version=v10.0 (win10-x86).
Some packages are not compatible with UAP,Version=v10.0 (win10-x86).
ParkSquare.Gracenote 1.3.0 is not compatible with UAP,Version=v10.0 (win10-x86-aot).
Some packages are not compatible with UAP,Version=v10.0 (win10-x86-aot).
ParkSquare.Gracenote 1.3.0 is not compatible with UAP,Version=v10.0 (win10-x64).
Some packages are not compatible with UAP,Version=v10.0 (win10-x64).
ParkSquare.Gracenote 1.3.0 is not compatible with UAP,Version=v10.0 (win10-x64-aot).
Some packages are not compatible with UAP,Version=v10.0 (win10-x64-aot).
Package restore failed for 'MyApp.UWP'.
Package restore failed. Rolling back package changes for 'MyApp.UWP'.
========== Finished ==========
At first sight we think that Gracenote is not compatible with Windows 10.
We're trying to include Gracenote in our app on Windows 10; in case it is possible, which APIs should we use?
In order to get the package compatible with UWP, you need to a) contact package's developer to update the package or b) fork the package and convert/build it for UWP.
You can also implement the REST API of Gracenote yourself.
I just upgraded to Meteor 1.2 from 1.1.
It did not upgrade and this is what it output
MacBook-Pro:ProjectX Nearpoint$ meteor update
Update to release METEOR#1.2.0.1 is impossible:
While selecting package versions:
error: Conflict: Constraint less#1.0.11 is not satisfied by less 2.5.0_2.
Constraints on package "less":
* less#=2.5.0_2 <- top level
* less#1.0.11 <- multiply:iron-router-progress 1.0.1
* less#1.0.0||2.0.0 <- matteodem:easy-search 1.6.3
* less#1.0.0||2.0.0 <- mdg:camera 1.1.5
This project is at the latest release which is compatible with your current package constraints.
npm-container: updating npm dependencies -- beagle, validator, async...
Changes to your project's package version selections from updating package versions:
cfs:http-methods upgraded from 0.0.29 to 0.0.30
ian:accounts-ui-bootstrap-3 upgraded from 1.2.79 to 1.2.80
matteodem:easy-search upgraded from 1.6.3 to 1.6.4
meteorhacks:kadira upgraded from 2.23.2 to 2.23.4
The following top-level dependencies were not updated to the very latest version available:
* kevohagan:sweetalert 0.5.0 (1.0.0 is available)
* mdg:camera 1.1.5 (1.2.0 is available)
* natestrauser:filepicker-plus 1.2.3 (2.0.0 is available)
* natestrauser:select2 3.5.1 (4.0.0_1 is available)
* zimme:iron-router-active 1.0.4 (2.0.1 is available)
Newer versions of the following indirect dependencies are available:
* babrahams:editable-json 0.4.3 (0.6.0 is available)
* matb33:collection-hooks 0.7.15 (0.8.0 is available)
* meteorhacks:aggregate 1.2.1 (1.3.0 is available)
* meteortoys:hotreload 0.2.0 (0.3.0 is available)
* meteortoys:listen 0.3.0 (0.4.0 is available)
* meteortoys:pub 0.3.1 (0.4.0 is available)
* meteortoys:status 0.1.0 (0.2.0 is available)
* meteortoys:toypro 0.4.2 (0.5.0 is available)
* softwarerero:accounts-t9n 1.0.9 (1.1.4 is available)
* tap:i18n 1.5.1 (1.6.1 is available)
* underscorestring:underscore.string 3.0.3_1 (3.2.2 is available)
To update one or more of these packages, pass their names to `meteor update`.
What should I do to fix this now? I currently cannot start my server after upgrading.
I am getting the error
=> Started proxy.
=> Started MongoDB.
=> Errors prevented startup:
While selecting package versions:
error: Potentially incompatible change required to top-level dependency: matteodem:easy-search 1.6.3,
was 1.6.4.
Constraints on package "matteodem:easy-search":
To allow potentially incompatible changes to top-level dependencies, you must pass
--allow-incompatible-update on the command line.
=> Your application has errors. Waiting for file change.