highcharts-ng: Cannot read property 'setExtremes' of undefined - angularjs

Suddenly highcharts-ng module started throwing out quite a strange error.
I did not touch this part of the code and I don't use setExtremes property.
Error Line 92:
If somebody already faced with such kind of problem I really appreciate your help.

This is a new bug introduced in 0.0.9 and only partially fixed in 0.0.10.
It will be fixed in a 0.0.11 shortly. In the meantime if in your chart config you define a yAxis it will work:
yAxis: {
events: {}
}

The problem was with highcharts-ng version update from 0.0.8 to 0.0.10
So we decided to do the simplest solution for now and downgrade to 0.0.8.
If you know how to solve the problem with new version - please post it here.

Related

List JS: `TypeError: list.templater is undefined`

I'm wondering if anyone has had an issue with or can help with TypeError: list.templater is undefined when using list.js, and how they solved it? A clue might be that I'm also getting an Source Map URL: list.js.map 404 / not found error.
If there's another better-used / better-documented package that does something similar to list.js, I'd definitely be open to that too.
Perhaps this question was a bit too much information, but it gives more context to what's going on.

React-Images and React-Photo-Gallery Compile Error

I am trying to install React-Photo-Gallery and React-Images to get a lightbox gallery.
I am getting this error:
Error in ./~/react-scrolllock/dist/index.js
Module not found: [CaseSensitivePathsPlugin] /Users/anmareewilliams/Apps/anmaree/anmaree/node_modules/react-scrolllock/dist/Scrolllock.js does not match the corresponding path on disk ScrollLock.js.
# ./~/react-scrolllock/dist/index.js 7:18-41
I am not sure what I did wrong because I didn't touch anyting related to the Scrolllock and I am seeing that the Scrolllock.js is in fact named dist/ScrollLock.js
Any help would be much appreciated.
Thank you.
You haven't done anything wrong so far.
React-Images is using an old version of react-scrollock (4.0.1 latest is 5.0.0), which might be a problem.

Property 'hot' is missing in type 'Module'

hello everyone when i use #types/node for aws-cognito-identity provider
i get the following error.
Class 'Module' incorrectly implements interface 'NodeModule'.
Property 'hot' is missing in type 'Module'.
Thanks for your help. I think it conflicts with #types/webpack-env
Looks like there might be a breaking change between #types/node#8.0.26 and #types/node#8.0.27 causing this error, probably in conjunction with #types/webpack-env#1.13.0 (my version at least).
Rolling back to 8.0.26 (adding "#types/node": "8.0.26" to my package.json) seems to fix it for now.
Edit:
Looking a bit closer, it seems this has been noticed and an issue raise:
https://github.com/DefinitelyTyped/DefinitelyTyped/issues/19601 + fix PR is open:
https://github.com/DefinitelyTyped/DefinitelyTyped/pull/19602
Are you trying something like, module.hot Then you can use it as (module as any).hot. This works for me.

$this->viewPath is not working with CakePHP 3.1

I have updated my cakePHP application to 3.1 through composer, and I'm trying to fix all the small or deprecated warnings.
I could easily fix the $this->layout stuff but I don't understand how to fix viewPath errors.
Looking at the migration guide it looks like it should be exactly the same thing:
$this->viewPath = 'Element';
should become
$this->viewBuilder()->viewPath('Element');
But this is not working, and the only thing that I get is
Error: Call to undefined method Cake\View\ViewBuilder::viewPath()
File /var/www/myapp/src/Controller/InvoicesController.php
Line: 375
What is the correct way to fix this?
From the very same migration guide, in the View section of it:
View::$viewPath is deprecated. You should use View::templatePath() instead.
Guess it's now:
$this->viewBuilder()->templatePath('Element');

Using UI hash key in an events hash

I am using marionette version 1.2.3 and backbone version 1.1.0
Here is my UI and events hash:
ui:{
title : '#modelTypeTitle'
},
events:
{
'change #ui.title' : 'validateTitle'
},
This seems to match what the documentation says:
"You can also use the ui hash values from within events and trigger keys using the '#ui.elementName'"
To clarify I want to know why what I am trying above does not work. but the following works fine:
events:
{
'change #modelTypeTitle' : 'validateTitle'
},
Okay, problem solved after you showed version.
This feature, parsing #ui. syntax within the events and triggers hash, is recently added in 1.4.0 in early December. See changelog: https://github.com/marionettejs/backbone.marionette/blob/master/changelog.md
Just update your Marionette version to the latest stable(1.4.1 currently) and problem should be solved.
*I just noticed this new feature thanks to your question. I don't feel comfortable at this point before, now solved. Another evidence of helping others could also help the man himself. :)

Resources