When I run both meteor add for both meteoric:ionic-sass and meteoric:ionicons.-sass, it shows the error below.
=> Errors while adding packages:
While checking for stevezhu:sass#1.3.7:
error: No compatible binary build found for this package. Contact the
package author and ask them to publish it for your platform.
I use a windows machine by the way..is that the problem? I have also posted on the Github page but I think it is not maintained or something.
I was having this issue with a different package while trying to work on a Windows machine. I ended up calling meteor update while in the directory for the meteor project I was working on and that fixed it.
Related
I am facing issues while using the react-native-vision-camera package for a small camera app. I encountered an error while building the app on Android which says "The Android Gradle plugin supports only kotlin-android-extensions Gradle plugin version 1.6.20 and higher.The following dependencies do not satisfy the required version: project ':react-native-vision-camera' -> org.jetbrains.kotlin:kotlin-gradle-plugin:1.5.30 and its failing my built on android."
I tried adding "kotlinVersion = "1.7.0" (under buildToolsVersion) to the android/build.gradle file but it gave me another error "Error: EPERM: operation not permitted." Running the commands as an administrator also did not work. I am using a Windows 10 machine with the latest version of Node.js and React Native.
Has anyone successfully set up the react-native-vision-camera package? I have followed the documentation but still facing these issues. It would be great if anyone could help me fix these errors and provide proper setup instructions.
I'm currently using chartjs-node to generate some charts. My node.js code runs perfectly on my local (windows) machine, but I suspect that's because I have windows-build-tools installed, which includes the cairo package.
When I push to my remote (linux) server and try to compile, I get the following error:
No package 'cairo' found
However, my package dependency list is as follows:
"canvas-prebuilt": "^1.6.5-prerelease.1",
"chart.js": "2.6.0",
"chartjs-node": "^1.6.1"
Based on my understanding from the documentation, using canvas-prebuilt instead of canvas should circumvent the need for any package pre-installation on my server. Obviously, I could just preinstall the necessary packages (as described in this SO answer) - but I'm wondering if there's any way to set up my package dependency list to avoid that route.
Thanks for your help!
You could switch chartjs-node to my chartjs-node-canvas package. It uses canvas-prebuilt instead of canvas, one of the main reasons for its existance :)
The project I am working on, works in the development environment. But when I deploy it live and navigate to the site, I only see blank screen.
I get the following errors in the console (from both development and production environment)
The same error exists in the development and production environments. The different is, I can navigate through the site pages in the development environment. But I only see a blank screen in the production environment.
I tried to update my jQuery to the latest version using the following command:
meteor npm install --save jquery meteor-node-stubs
But I still get the same error.
What am I doing wrong here?
This issue cost me some time to work out. Basically you need to find a sweet spot for jquery.
Meteor loads jquery by default, and in .meteor/packages I have jquery#1.11.10, which is probably what Meteor puts in for you.
You will also need to load a version somewhere in between that works. For me this command did the trick:
meteor npm install jquery#2.2.4
Cheers
So I am very new to Meteor, and I was sifting through some example apps and open source projects when I came across this simple chat application:
(https://github.com/BenderV/simplechat)
I wanted to download the project, run it on my local server, and mess around with the code to learn more about what does what, and how to use the Meteor framework. I simply downloaded the .zip file from github and tried to run it (using the meteor in my terminal. However I got the following error when I ran the application locally in my browser:
Your app is crashing. Here's the latest log.
=> Errors prevented startup:
While building the application:
error: no such package: 'accounts-guest'
error: no such package: 'user-status'
error: no such package: 'accounts-testing'
error: no such package: 'fontawesome4'
error: no such package: 'iron-router'
error: no such package: 'bootstrap-3'
error: no such package: 'fast-render'
error: no such package: 'jquery-titlealert'
error: no such package: 'related'
=> Your application has errors. Waiting for file change.
I can (obviously) infer from the nature of the log that the error that I am experiencing is because I don't have the correct packages installed (the one that are listed, obviously).
So keeping this in mind, I researched how to add packages to meteor (using instructions I found on Atmosphere JS pages of the respective packages). However, when I entered the command that was provided by Atmosphere into my terminal (for example for, 'accounts-guest' package I entered: meteor add artwells:accounts-guest). Unfortunately doing this did not work, and I was given something like the following error in the terminal: artwells:accounts-guest: no such package
I have no idea what to do, the packages will not install so I can not try this code. I come from experience with Rails, and in Rails if you needed to install "gems" (pretty much the same thing as packages in Meteor) you could just enter bundle install into the terminal to download and install undefined packages. Is there something like this in Meteor? I have heard of something called Meteorite, but am unsure what it is and how to use it.
Anyways I really would appreciate any help in getting me past this minor roadblock on my way to learning Meteor!
Thank you
That's an older project which use the old packaging system 'meteorite' = 'mrt' on the command line.
I suggest you try a newer example, Meteor ships with a few. Once you have Meteor installed you can create an example app by typing one of the following commands :
meteor create --example leaderboard
meteor create --example todos
meteor create --example localmarket
And yes, there is a very similar mechanism to the gems commands you are accustomed to. Simply running a project 'meteor' should download its dependencies. Also you can run 'meteor update' if you want to update to the latest versions for your project.
Last August there was a major update to the meteor package management system, you can read more about it here : https://www.meteor.com/blog/2014/08/26/meteor-090-new-packaging-system
So, for any examples you'd like to check out, try and get a recent one, from meteor 1.0. In newer versions of meteor those instructions on Atmosphere should work out fine for you.
You can see what version of meteor a project is running by looking at this file ".meteor/release" inside a meteor project :
https://github.com/BenderV/simplechat/blob/master/.meteor/release
so you can see that one is old.
good luck!
I guess the better question here is more general: how do I debug errors for deployed apps? Does Meteor have commands/logs I can look at? I'm really not sure where to begin because everything works fine locally.
I'm getting this error in the browser console when I try to view the Meteor app I deployed to *.meteor.com. Output is a blank screen, but locally, the same code results in no errors and output is normal.
Has anyone seen this before? There's a thread connecting this to accounts-ui-bootstrap-3 but I'm not using that.
For reference, I'm using Meteor 0.8.1.3, blaze-layout 0.2.4, iron-router 0.7.1, and accounts-entry 0.7.3.
EDIT: looking at meteor logs right now but nothing constructive so far.
Same issue, in same places (prod but not dev). Running mrt update and meteor update fixed it for me.
Are you using meteorite? Try adding blaze-layout:
mrt add blaze-layout
And check in .meteor/packages that it loads after iron-router.
Then deploy as usual to *.meteor.com
I encountered this issue after updating to the latest meteor with:
$ sudo meteor update
Read through several posts, and found my issue was caused by not running the update through Meteorite:
$ sudo mrt update
This fixed the slew of errors I encountered.
Also, I had to remove the package blaze-layout, which I had manually added through mrt as suggested above, because it caused a recursive dependency with with iron-layout.