Meteor Suddenly a lot of packages do not work (possible because of meteor update) - meteor

I;ve been developing a quizz app recently and it was working consistently but now suddenly a lot of packages are not defined. A small part of the error log below (this goes on to contain most of the packages)
Uncaught ReferenceError: Package is not defined meteor.js? 7a66be7a03504cd2c18dd47b699e6233b60675ed:21
Uncaught ReferenceError: Package is not defined json.js?e22856eae714c681199eabc5c0710b904b125554:21
Uncaught ReferenceError: Package is not defined ejson.js?9ccd48dbafd805e21408c9eae1061468b3ec1f2f:21
Uncaught ReferenceError: Package is not defined logging.js?
Other interesting errors:
Uncaught ReferenceError: Deps is not defined quiz_list.js?b063b352079e20c9f9485683b352f8482a87fdf4:4
Uncaught ReferenceError: Template is not defined
Does anyone know what is causing this and how I can remedy it? I have tried resetting and updating.

I often get a whole slew of these types of errors as a result of one uncaught exception right at the top. If things don't happen in the right order, then things really don't happen.
Try scrolling right up and seeing if there is a more informative error (not always shown in red in Chrome).

Related

Require() of ES Module Konva

I am trying to copy this sandbox. I copied everything and installed Konva, use-image and react-konva, but I got 2 errors. The first is that canvas is missing so I installed that. After the installation,I got this error:
Error [ERR_REQUIRE_ESM]: require() of ES Module C:\User\Folder\node_modules\konva\lib\Core.js from C:\User\Folder\node_modules\react-konva\lib\ReactKonvaCore.js not supported.
I am using Next13.
The error itself happens in a weird sense. If I navigate to the page from any link it works, but if I refresh the page, I get the errors.

Uncaught TypeError: Cannot read property 'register' of undefined

I'm using pushpad.xyz for push notifications in my wordpress project. I added pushpad code but I get this error which I can't understand.
pushpad.js:292 Uncaught TypeError: Cannot read property 'register' of undefined
at Object.registerServiceWorker (pushpad.js:292)
at Object.init (pushpad.js:261)
at init (pushpad.js:362)
at window.pushpad (pushpad.js:548)
at pushpad.js:551
at Array.forEach (<anonymous>)
at pushpad.js:550
at pushpad.js:553
Could some one explain why I'm getting this error. Because this error is coming only in this wordpress project which I'm running in a virtual machine using vagrant. Is this the reason for the error? If yes how can I fix it?
The relevant line in pushpad.js that raise the error is the following:
navigator.serviceWorker.register(_.options.serviceWorkerPath, { updateViaCache: 'none' });
Thus the error indicates that navigator.serviceWorker is undefined: probably you are using an old or buggy browser version.

JMS Call to a member function has() on null

Bundle version 1.3.1
| Symfony version 3.3
| PHP version 7.1.9
Expected behavior
After installing the different bundles (JMSTranslationBundle, JMSDIExtraBundle, checking if i had sensio/framework-extra-bundle), and after i made the right configuration in config.yml and routing_dev.yml, the right behavior should be that the /_trans lead me to a translation interface (working), and change nothing else.
Actual behavior
Getting on a route different from /_trans return Call to a member function has() on null with error 500. Therefore, the whole site is dead, except the translation UI.
Steps to reproduce
Install JMSTranslationBundle, then when asked, install JMSDIExtraBundle to get the web ui
After that, test the /_trans. This should work. But when you get to your others routes, they return 500 error
I have exactly the same issue (Sf 3.3.9/PHP 7.1.9). I have to remove the line related to "JMSDiExtraBundle" in AppKernel to make my app works again. This is the only workaround I found, not very efficient.
Very low trace log information, this is what I have:
Stack Trace:
Logs:
CRITICAL 19:56:59 php Call to a member function has() on null
CRITICAL 19:56:59 request Uncaught PHP Exception Symfony\Component\Debug\Exception\FatalThrowableError: "Call to a member function has() on null" at /Users/stephanfo/PhpstormProjects/openbuy/vendor/symfony/symfony/src/Symfony/Bundle/FrameworkBundle/Controller/ControllerTrait.php line 233
Exception:
Any help would be helpful.
Thanks,
Stef.

App is broken after 0.9.4 update: undefined is not a function in dynamic_template.js:371

I had a meteor 0.9.3 app that was working.
I ran meteor update. Now I have a bunch or errors (60 total):
Uncaught TypeError: undefined is not a function dynamic_template.js:371
Uncaught TypeError: Cannot read property 'prototype' of undefined helpers.js:140
Uncaught TypeError: undefined is not a function router.js:61
Uncaught TypeError: Cannot read property 'RouteController' of undefined iron-router-progress.js?2b52a697e5a2fba4ec827721c08cfdd0a5bae508:25
Uncaught TypeError: Cannot read property 'RouteController' of undefined global-imports.js?a26cc176b56b3d2b1df619ec7af99630b0fb6a1f:3
Uncaught ReferenceError: Template is not defined template.about.js?3ead3e2cab8a60252235e31f2533c2179f736294:2
Uncaught ReferenceError: Template is not defined template.register.js?60e4180bd0193951fab290d41493f5036f66240d:2
... 53 more errors:
... mainly "Template is not defined" and "Meteor is not defined"
Line 371 of dynamic_template.js is the following:
UI.registerHelper('DynamicTemplate', Template.__create__('DynamicTemplateHelper', function () {
What's wierd is that if I try to go back with meteor update --release 0.9.3 or 0.9.2, I still have those errors. So I'm stuck, I have to fix those.
Another anoying thing is that everytime I start my meteor server, I get updating package catalog with a progress bar, and my server takes a while (~10s) to start up.
Any ideas?
In 0.9.4 there are changes to the templating API. See HISTORY.md on gihub/meteor/meteor for more details.
The fix for your immediate problem is to replace UI with Template
Template.registerHelper('DynamicTemplate', Template.__create__('DynamicTemplateHelper', function () {

Error after upgraded to Meteor 0.9.1

After upgraded Meteor from 0.9.0.1 to 0.9.1, I got the following errors in console:
Uncaught TypeError: Cannot read property 'registerHelper' of undefined
Uncaught TypeError: Cannot read property 'T9n' of undefined
Uncaught TypeError: Cannot read property 'AccountsEntry' of undefined
Uncaught ReferenceError: Template is not defined
Uncaught ReferenceError: Meteor is not define
Exception in defer callback: ReferenceError: Spacebars is not defined
It seems that the changes are not backwards compatible.
It sounds like you have a package that is not compatible. To check what this is look at your server console.
If you want to brute force your way into getting it to work, git clone the offending package into /packages and it should get it to work (also add it with meteor add xx where xx is the name of the directory in /packages
Additionally rename the following (even though you would not yet have to) to bring it up to date:
UI.registerHelper -> Template.registerHelper
Handlebars.registerHelper -> Template.registerHelper

Resources