package alanning:roles at 1.0.6 is incompatible with Meteor 0.9.0 or later - meteor

My meteor version is 1.4.1.1 and have used my personalised package in which I am using alanning:roles (api.use(alanning:roles))
I am getting the following errors on my command prompt:
W20161111-16:24:34.950(5.5)? (STDERR) The package mizzao:user-status at 0.2.0 is incompatible with Meteor 0.9.0 or later.
W20161111-16:24:35.473(5.5)? (STDERR) If a new, compatible version of this package exists, running 'meteor update' should cause you to update.
W20161111-16:24:35.474(5.5)? (STDERR) The package alanning:roles at 1.0.6 is incompatible with Meteor 0.9.0 or later.
W20161111-16:24:35.474(5.5)? (STDERR) If a new, compatible version of this package exists, running 'meteor update' should cause you to update.
=> Started your app.
What am I doing wrong?

Got the answer simply write below command in your meteor project command prompt:
meteor update alanning:roles

Related

Meteor don't run after update to 2.7.3 from 2.2 - AccountsTemplates Error

I remove useraccounts:core from my project to update at the last version of meteor and than add again useraccounts:core when I have update to 2.7.3, but now meteor don't run.
Like the title, there is this error in promise_server.js and AccountTemplates have you any suggestions ?
=> Started proxy.
=> Started MongoDB.
W20220812-16:05:04.937(2)? (STDERR) /home/----/.meteor/packages/promise/.0.12.0.7cv555.76nvp++os+web.browser+web.browser.legacy+web.cordova/npm/node_modules/meteor-promise/promise_server.js:218
W20220812-16:05:04.966(2)? (STDERR) throw error;
W20220812-16:05:04.967(2)? (STDERR) ^
W20220812-16:05:04.967(2)? (STDERR)
W20220812-16:05:04.968(2)? (STDERR) Error: AccountsTemplates: You must add at least one account service!
W20220812-16:05:04.968(2)? (STDERR) at AT._init (packages/useraccounts:core/lib/server.js:19:11)
W20220812-16:05:04.969(2)? (STDERR) at packages/useraccounts:core/lib/server.js:183:21
W20220812-16:05:04.969(2)? (STDERR) at Function.time (/home/----/Documenti/GitHub/prevenzionecantieri/.meteor/local/build/programs/server/profile.js:273:30)
W20220812-16:05:04.970(2)? (STDERR) at /home/----/Documenti/GitHub/prevenzionecantieri/.meteor/local/build/programs/server/boot.js:415:15
W20220812-16:05:04.970(2)? (STDERR) at /home/----/Documenti/GitHub/prevenzionecantieri/.meteor/local/build/programs/server/boot.js:465:7
W20220812-16:05:04.971(2)? (STDERR) at Function.run (/home/----/Documenti/GitHub/prevenzionecantieri/.meteor/local/build/programs/server/profile.js:280:14)
W20220812-16:05:04.971(2)? (STDERR) at /home/----/Documenti/GitHub/prevenzionecantieri/.meteor/local/build/programs/server/boot.js:463:13
=> Exited with code: 1
Where is the problem ?
I have try with:
meteor add brettle:accounts-add-service
but I have this error:
=> Errors while adding packages:
While selecting package versions:
error: Conflict: Constraint accounts-base#1.2.0 is not satisfied by accounts-base 2.2.4.
Constraints on package "accounts-base":
* accounts-base#~2.2.3 <- top level
* accounts-base#2.1.0 <- useraccounts:core 1.16.2
* accounts-base#2.2.0 <- service-configuration 1.3.0 <- accounts-base 2.2.4 <- accounts-ui 1.4.2
* accounts-base#2.2.0 <- accounts-ui 1.4.2
* accounts-base#2.2.2 <- accounts-ui-unstyled 1.7.0 <- accounts-ui 1.4.2
* accounts-base#1.2.0 <- brettle:accounts-add-service 0.2.0
* accounts-base#1.2.0 <- brettle:accounts-multiple 0.0.8 <- brettle:accounts-add-service 0.2.0
I have solved:
Meteor reset
meteor add fetch
meteor add accounts-ui
meteor add service-configuration
meteor add accounts-password
meteor add accounts-ui
Now work, I have to restore the database locally but meteor run
Glad you solved the issue! Can you mark your question as Solved? So it's easier for people find it
Thanks

Error while upgrading from 1.4.4.2 to 1.4.4.3 or higher

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.

Error after updating from 0.8.3 to 0.9.2

I've updated from 0.8.3 to the latest version (0.9.2) and I've received this error. I have gone so far as to create a new meteor (0.9.2) project, and transfer all of my code from the old project, then freshly install all packages required.
/Users/nathaniel/Desktop/ESOS/.meteor/local/build/programs/server/packages/meteorhacks_kadira.js:2682
throw err;
^
ReferenceError: Router is not defined
at app/common/router.js:1:36
at app/common/router.js:177:3
at /Users/nathaniel/Desktop/ESOS/.meteor/local/build/programs/server/boot.js:161:10
at Array.forEach (native)
at Function._.each._.forEach (/Users/nathaniel/.meteor/packages/meteor-tool/.1.0.31.sw6o3m++os.osx.x86_64+web.browser+web.cordova/meteor-tool-os.osx.x86_64/dev_bundle/lib/node_modules/underscore/underscore.js:79:11)
at /Users/nathaniel/Desktop/ESOS/.meteor/local/build/programs/server/boot.js:82:5
=> Exited with code: 7

Not able to install iron-router to meteor version 0.9.1

Today only i updated the meteor version to 0.9.1 but i am not able to install iron-router to my new project created by using the command
meteor add iron:router
the error i get is:
downloading iron:dynamic-template at version 0.3.0 ...
/root/.meteor/packages/meteor-tool/.1.0.26.13pjtg1++os.linux.x86_32+web.browser+web.cordova/meteor-tool-os.linux.x86_32/dev_bundle/lib/node_modules/fibers/future.js:206
throw(ex);
^
[Offline: Error: SELF_SIGNED_CERT_IN_CHAIN]
i also tried to revise my meteor back to older version to 0.8.3 and used mrt then also can't able to install iron-router. Please tell me how to install iron-router for meteor version 0.9.1.
This is possibly due to broken pipe in connection. I was getting similar errors. Try closing the terminal window and run the update again and should run smoothly. Even if you get errors just try to run 2-3 times till all the packages are downloaded and updated.

Meteor update to 0.8.3 breaks app

Today I updated my Meteor project to version 0.8.3
$> [master●] % mrt update
✓ normalize.css
branch: https://github.com/rithis-archive/meteor-normalize.css.git#master
✓ Meteor.cron
branch: https://github.com/alexsuslov/Meteor.cron.git#master
✓ iron-router
tag: https://github.com/EventedMind/iron-router.git#v0.9.1
✓ mongodb-server-aggregation
tag: https://github.com/zvictor/meteor-mongo-server.git#v1.0.3
✓ reactive-publish
tag: https://github.com/Diggsey/meteor-reactive-publish.git#v0.1.6
✓ reststop2
tag: https://github.com/Differential/reststop2.git#v0.6.0
✓ kadira
tag: https://github.com/meteorhacks/kadira.git#v2.4.13
✓ subs-manager
tag: https://github.com/meteorhacks/subs-manager.git#v1.0.2
✓ async
tag: https://github.com/peerlibrary/meteor-async.git#v0.9.0-1
✓ npm
tag: https://github.com/arunoda/meteor-npm.git#v0.2.6
✓ iron-layout
tag: https://github.com/EventedMind/iron-layout.git#v0.2.0
✓ server-deps
tag: https://github.com/Diggsey/meteor-server-deps.git#v0.1.2
✓ blaze-layout
tag: https://github.com/EventedMind/blaze-layout.git#v0.2.5
✓ iron-core
tag: https://github.com/EventedMind/iron-core.git#v0.2.0
✓ iron-dynamic-template
tag: https://github.com/EventedMind/iron-dynamic-template.git#v0.2.1
Done installing smart packages
Now when I run it $> mrt I get the following output:
Stand back while Meteorite does its thing
Done installing smart packages
Ok, everything's ready. Here comes Meteor!
[[[[[ ~/tmp/test ]]]]]
=> Started proxy.
=> Meteor 0.8.3 is available. Update this project with 'meteor update'.
=> Started MongoDB.
iron-router: updating npm dependencies -- connect...
kadira: updating npm dependencies -- debug, usage...
=> Errors prevented startup:
While building package `iron-router`:
error: no such package: 'reactive-dict#1.0.0'
error: no such package: 'deps#1.0.0'
error: no such package: 'underscore#1.0.0'
error: no such package: 'ejson#1.0.0'
error: no such package: 'jquery#1.0.0'
error: no such package: 'ui#1.0.0'
error: no such package: 'iron'
error: no such package: 'cmather'
error: no such package: 'webapp#1.0.0'
=> Your application has errors. Waiting for file change.
Now when I do meteor update the problem remains. Even if I first do meteor update and then mrt update I end up with the same result. Any suggestions ?
The problem is that running mrt update has updated iron:router to the latest version (0.9.1), which is only compatible with meteor 0.9 release candidates (see the explanation here : Installation issues with iron-router (newest) on Windows 7 x64 (Meteor 0.8.3)).
What you need to do is downgrading iron-router to 0.8.2 which is compatible with meteor 0.8.3.
To do so, you'll have to modify your smart.json like this :
{
"packages": {
"iron-router":{
"version": "0.8.2"
}
}
Then clean your project by removing smart.lock and run mrt install to make sure meteorite has accounted for the change.
If everything is OK the iron-router version symlinked in your project packages folder should point to iron-router#0.8.2

Resources