Aziz Gazanchiyan
Aziz Gazanchiyan
@pamapa Will check, thanks. P.S. Could it be because of React 18 having Strict mode on in development? I see this change hitting a lot of people these days :)
It also breaks `image-minimizer-webpack-plugin`: ``` WARNING in Unknown plugin: imagemin-svgo Did you forget to install the plugin? You can install it with: $ npm install imagemin-svgo --save-dev $ yarn add...
You can use package mapping in your `package.json` until this is merged ```json "dependencies": { "@types/google.maps": "3.48.5", "@types/googlemaps": "npm:@types/[email protected]" } ```
@mikeedwards could you help us please with this?
We can also use [patch-package](https://www.npmjs.com/package/patch-package), but still...
@netil yeah, your are right. If I rename data names to be ``"_30", "_20", "_10"`` - I receive expected ordering. Should be some type casting issue I assume.
@netil Can't you read proper order from the ``columns`` entries? Like, finding index of a key from that array? I can change my code so keys are not castable to...
@netil Well, sure I can do that, but I'm sure this is something that has to be done by the library, not by me trying to hack the default behavior.
Another option is to use [office-addin-dev-certs](https://www.npmjs.com/package/office-addin-dev-certs). ```js const devCerts = require('office-addin-dev-certs'); return { devServer: { https: await devCerts.getHttpsServerOptions() } };
@hulkish I've installed ``node-voo`` globally, so yes - it is accessible. And I can run ``node `` with no problems. It is only ``npm`` fails.