meteor moment TypeError: n is undefined - meteor

I'm using this package :
https://github.com/acreeger/meteor-moment
The timezone function , moment.tz() , throws error "TypeError: n is undefined".
The function throws the error for most inputs, including basic examples from the moment timezone documentation website : http://momentjs.com/timezone/docs/
e.g. :
moment.tz("2013-12-01", "America/Los_Angeles").format(); will throw the error.

turns out there was already another version of moment timezone already being included in the project in the
/lib
folder.
I removed the old /lib version.
The Meteor packaged version https://github.com/acreeger/meteor-moment works fine.

Related

Project raised exception class EFilerError with message 'A class named TdxPNGImage already exists'

I have upgraded my environment from Embarcadero Berlin to Alexandria. After the upgrade, when I am running one of my project, I am getting multiple runtime errors:
A class named TdxPNGImage already exists
A class named TdxSmartImage already exists
and similar errors.
I have found that this error is coming from one of the DLLs that my project is using.
Can anyone please suggest how to fix this issue?

Error with context.scriptLoader in next js 10

I'm getting this error when running my NextJS app
TypeError: Cannot read property 'eager' of undefined
at Head.getPreloadMainLinks (/Users/someuser/dev/temp/next-js-10-1-error/mobile/.next/server/pages/_document.js:4936:30)
at Head.render (/Users/someuser/dev/temp/next-js-10-1-error/mobile/.next/server/pages/_document.js:5160:130)
My app was working fine in next js 10.0.1 but does not work on 10.1.3
I created an MVE here: https://github.com/jeznag/next-js-10-1-error
I'm not sure it is a bug in next as even if I revert to 10.0.1 in the MVE, I still get the error. (But in my real app on 10.0.1 I don't get an error)

expo and firestore, unhandled promise rejection: typeError

I have been getting this error for the last two days now.
This happened after I installed a node module named "faker". What I've found out until now is that npm 5 deleted any packages from the package.lock.json that were not installed using npm 5.
Hence I deleted node modules and the package.lock.json and did an npm install, it didn't help.
I created a separate expo project and copied the files over to it from the old project and installed every module again, it still does not work.
Below is the error I am getting:
[15:18:35] [Unhandled promise rejection: TypeError: undefined is not a function (evaluating 'collection[typeof Symbol === "function" ? Symbol.iterator : "##iterator"]()')]
- node_modules/#firebase/firestore/dist/index.cjs.js:8293:17 in forEach
- node_modules/#firebase/firestore/dist/index.cjs.js:13322:42 in onTransactionCommitted
- ... 52 more stack frames from framework internals

Error on meteor project setup

I setup meteor environment
meteor create todoapp
cd todoapp
Then write meteor and press enter after then I run on localhost:3000 then I receive following error on terminal
Exception from sub meteor_autoupdate_clientVersions id fRm2pMK35Ji2uPut5
TypeError: Cannot read property 'OneOf' of undefined
I don't know what the actual reason of this issue any way I found a solution I uninstalled Meteor the reinstalled it after this the issue has been resolved.

symfony 2.8 debug fatal error double message

Environment: Symfony 2.8.1 with XAMPP Version 5.5.24 on Windows 7.
If I trigger a fatal error in a controller, anything as simple as $array = ; in production environment, I'm getting a default php error:
Parse error: syntax error, unexpected ';' in C:\xampp\htdocs\tgsupport-test\src\AppBundle\Controller\DefaultController.php on line 16
followed by symfony custom error page message. Obviously I'd want to avoid to show eorr info in production.
Moreover in prod.log I see a double critical error: under php.CRITICAL and request.CRITICAL. Is really useful to show the same error twice?
I'm using default configuration, indeed I just installed default framework without any custom setting and I triggered my error in AppBundle/DefaultController, so I was wondering if I'm missing anything.
I missed a php.ini configuration to avoid to display error messages in page.

Resources