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.
Related
Im using ember to develop a project.
Please help me with this error. Im unable to run my project on local. After hitting
ember server the build is successful. But on hitting the http://localhost:4200
Loads empty page with console error.
Uncaught Error: Assertion Failed: The initializer 'App Version' has already been registered
at assert (index.js:172)
at Function.initializer (index.js:420)
at registerInitializers (index.js:27)
at loadInitializers (index.js:68)
at Module.callback (app.js:25)
at Module.exports (loader.js:106)
at requireModule (loader.js:27)
at app-boot.js:3
Unable to understand what to do. Any help regarding this would be appreciated.
I did a code search to see where that initializer might exist and it looks to be part of ember-cli-app-version.
In your place I would remove ember-cli-app-version from your app with npm uninstall --save-dev ember-cli-app-version and then run ember serve again. The purpose of this addon is to make it easy to see your app's version number in the ember inspector, but that's not a big deal so removing it won't break anything and should get you moving forward.
If you want to investigate the issue further try searching your code base (including node_modules) for App Version to see where a duplicate exists.
Running npm install solved the problem.
The actual issue was due to the iCloud sync being active in my Macbook.
Turning iCloud sync off should solve the problem.
My code: https://github.com/who-know-cg/main-gatsby
Every time I build my Gatsby app (on Zeit) I get this error message:
ERROR #11321 PLUGIN
"gatsby-transformer-json" threw an error while running the onCreateNode lifecycle:
Could not find function loadNodeContent for plugin gatsby-source-buttercms
Error: Could not find function loadNodeContent for plugin gatsby-source-butter cms
And I never meet this error when in developing using gatsby develop.
Here is a similar question on github https://github.com/ldd/gatsby-source-github-api/issues/10 .
But I don't know what the answer means, and I don't know if it's the same issue either.
Please help me find what part is going wrong, thanks you.
If you haven't gotten an answer yet there is a temporary workaround this issue. The github you've linked itself is very helpful.
Take the source code and use it as a local plugin.
https://www.gatsbyjs.org/docs/creating-a-local-plugin/
Change the mediaType in the source code from application/json to text/plain. This should be a working temporary solution.
this works for me
npm install Pearce-Ropion/gatsby-source-apiserver#6112115 -D
yarn add Pearce-Ropion/gatsby-source-apiserver#6112115 -D
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
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.
I'm revisiting "Discover Meteor" and ran into an error when installing the iron-router package. Currently running on MeteorJS v1.1.0.2. Here's the command line:
$mrt add iron-router
This caused all kinds of debugger errors, which I thought could be related to a dependency crash. However,
$mrt remove iron-router
leaves a dependency reference somewhere. Hence, the server crashes.
Anybody know where I can find the proper location for editing out the offending dependency?
That should be:
meteor add iron:router
As for removing old packages, you can edit the .meteor/packages file directly and remove anything you don't want. If you want to go back to how the project was at the start (in other words, make it look like it was after you first ran the meteor create command) leave these packages:
meteor-platform
autopublish
insecure