I run the following command for camera package.
meteor add mdg:camera
The following issue is getting triggered when I run meteor run in ubuntu terminal.
Errors prevented startup:
While building for web.browser:
error: no plugin found for camera.less in mdg:camera; a plugin for *.less was active when it was published but none is now
=> Your application has errors. Waiting for file change.
My meteor version is 1.4.0.1
Add one of the many available less packages to your application. For example:
meteor add less
remove both less and mdg:camera from package.json
then after meteor as removed and restarted app add
less#2.6.5
mdg:camera#1.4.1
solves the issue
Downgrade to 1.3.2.4
I just had the same problem, started working after downgrade.
Related
On a fresh install of Meteor 1.6, I am trying to add the angular2-compilers package to a new meteor app i.e.
meteor create v16app
cd v16app
meteor add angular2-compilers
Which fails as follows;
=> Errors while adding packages:
While loading package angular2-compilers#0.6.6:
error: Command failed: C:\WINDOWS\system32\cmd.exe /c
C:\Users\rober\AppData\Local\.meteor\packages\meteor-tool\1.6.0\mt-os.windows.x86_64\dev_bundle\bin\npm.cmd rebuild --update-binary
Cannot download "https://github.com/sass/node-sass/releases/download/v3.8.0/win32-x64-57_binding.node":
HTTP error 404 Not Found
I have only noticed this problem whilst upgrading from 1.5.2.2.
How do I resolve this? Any help appreciated.
We released a new version of the compilers.
Now, like Angular, they are just angular-compilers instead of angular2-compilers.
It now works way better and supports all the nice things from Angular like AOT compilation, Angular Universal and SSR and lazy loading.
Check out a couple of example apps here - https://github.com/Urigo/angular-meteor/tree/master/examples/MeteorCLI
I created a new app using below command;
meteor create --full test
The link application works fine. But then, I added aldeed:autoform to the project and re-run meteor.
the browser console shows error
Error : There is no route for the path: /
and the entire UI is blank.
NOTE: When I remove the package, the application works fine.
AutoForm 6.0 requires switching your app to using the SimpleSchema package from 'NPM' and aldeed:collection2-core package.
I encountered the same problem as yours, so when I ran command npm install simpl-schema, the error in the console went away.
Note: The aldeed:autoform was also looking for mongo-object which is present in simpl-schema from NPM. For better understanding, follow the below image attached.
Hope this helps.
I am running a Meteor 1.4.2.3 application and everything has been running fine so far. I have been following the Level Up Tutorials and I've come to a point where I want to add user accounts.
In order to do that I'm using the `okgrow:accounts-ui-react' atmosphere package which can be found here.
I've followed all the steps by running the following 3 lines in the console:
> meteor add okgrow:accounts-ui-react
> npm install --save react-komposer classnames
> meteor add accounts-password
Those commands all ran successfully.
Now when I want to start my Meteor application by running meteor in the console I get the following error:
Does anyone know what I could be doing wrong?
Things I have tried that haven't solved it:
Updating all my meteor packages using the meteor update --all-packages command
Deleting the node_modules folder and running 'meteor' again.
The issue here is that React Komposer completely changed their api in the latest version for some reason. There is an outstanding issue regarding this here:
https://github.com/okgrow/accounts-ui-react/issues/4
In the meantime, I'd suggest https://github.com/studiointeract/accounts-ui as development has continued on it again.
Meteor example app, microscope has version 0.9.4, when I try use meteor run command to launch application .
There have a print:
Sorry, this project uses Meteor METEOR#0.9.4, which is not installed and
could not be downloaded. Please check to make sure that you are online.
I am behind a proxy in corporate.
When I install the Meteor, only latest 1.0.0 can be installed.
How can I do?
Upgrade the app to 1.0.0, and how?
Downgrade the meteor to 0.9.4, and how?
I tried use meteor update --release 0.9.4, not work or using meteor update, other error pop up:
/home/hunter/.meteor/packages/meteor-tool/.1.0.35.hgbesu++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);
..
Error: tunneling socket could not be established, cause=socket hang up
at Object.Future.wait (/home/hunter/.meteor/packages/meteor-tool/.1.0.35.hgbesu++os.linux.x86_32+web.browser+web.cordova/meteor-tool-os.linux.x86_32/dev_bundle/lib/node_modules/fibers/future.js:326:15)
at _.extend._createSocket (packages/ddp/stream_client_nodejs.js:265)
at _.extend._launchConnection (packages/ddp/stream_client_nodejs.js:142)
at new LivedataTest.ClientStream (packages/ddp/stream_client_nodejs.js:28)
at new Connection (packages/ddp/livedata_connection.js:52)
at Object.DDP.connect (packages/ddp/livedata_connection.js:1581)
This should proxy issue.
No document there after search.
I was able to successfully update a project from 0.9.3.1 to 1.1 with:
meteor update
Using meteor run like this:
meteor run --release
…won’t upgrade your meteor installation, but will download the --release and run the current app with it.
I had similar issue after updating meteor to 1.4.1. I happened to fix it with this help Github Issue
Reset your app
meteor reset
Install npm with meteor again
meteor npm install
Rebuild npm (Optional)
meteor npm rebuild
This is a bit late and slightly different: I have a similar problem when I upgraded from 1.0.3.1 to 1.0.3.2. After reading the answers here, and here, I tried the following which worked for me:
meteor update --release <new version>
replacing <new version> with the latest version you're running. This updated my project, and subsequent runs using meteor works as expected.
I was to update by change the file .meteor/release to meteor 1.0. I had packages issues, I also noticed that iron router inner actions changed (I fixed this by fixing the files load order) and on Meteor 1.0 you’ve a package for everything.
Try to add the package meteor-platform, it’s a meta package that contains the most used packages.
I also had issue with some atmosphere packages, it’s a tough job to upgrade it.
I think updating Meteor might have broken my app. It was working, then I ran meteor update, and now it is not working. Can I do something like meteor downgrade?
Meteor 0.6.0 and above ships with a new distribution system. You can now pass the --release argument to any Meteor command and it will run against the requested release. For example, to bundle your app against Meteor 0.6.1, run: meteor bundle --release 0.6.1. Notably, this only works for post-0.6.0 releases.
If you want to pin your app to a specific release, run: meteor update --release <release>. This modifies the .meteor/release file in your app directory. Then simply run Meteor as usual. You'll still get notified when there's a new release available.
UPDATE: As of Meteor 0.6.0, this functionality is available without using Meteorite. See Avital's answer. (for versions > 0.6.0. To use functionality on versions less than 0.6.0 you can still use Meteorite:
If you want to control versions with your apps (so your existing app can still use an older version, or 0.57.1 (with the security bug fix) you can use meteorite: https://github.com/oortcloud/meteorite
Install it via npm install -g meteorite
Its also helpful with loads of other packages from http://atmosphere.meteor.com.
To control the version of your app edit your smart.json to something with:
{
"meteor": {
"tag": "v0.5.7"
}
}
Only the app you've already made will be affected & you can upgrade it when you're ready.
I have tried this and it is very hard. My best advice is to try and copy all the files from an app running the version you want, then paste your app's code in there.
There is no meteor downgrade command from its CLI. The best and easy way if you have version control like GIT, just undo your recent changes by git stash save, and run meteor again.
On Windows, I was able to effectively "downgrade" from a failed upgrade by editing the version number to a previous working release in the file:
C:\Users\Paul\AppData\Local.meteor\meteor.bat
You need to change it to a version which has a corresponding folder in: .meteor\packages\meteor-tool