react-tooltip | react tooltip component | Frontend Utils library

You need to use a schema type like Yup.string() or Yup.number() before you can use required().

Only schemas have the required prop:

As far as I can see, you upload the image and get its download URL in this snippet:

It's difficult to guess what's going on, as you pointed it seems related to cache issues, however, you've tried all the cache-related stuff. I'd suggest:

• Remove gatsby-plugin-offline and add gatsby-plugin-remove-serviceworker since you won't be using service-workers anymore

• Check the importation path. It should be:

Give custom class to your tooltip using data-class attribute

In our case we were setting the draco decoder path to:

https://www.gstatic.com/draco/v1/decoders/

by calling:

this.dracoLoader.setDecoderPath("https://www.gstatic.com/draco/v1/decoders/");

But their recommended way is specifying the version in the URL:

https://www.gstatic.com/draco/versioned/decoders/1.4.3/

They released a new version yesterday, which explains the sudden errors: https://github.com/google/draco/releases/tag/1.4.3

Changing to the versioned URL fixed it for us. Another fix that worked was using JS instead of Webassembly:

this.dracoLoader.setDecoderConfig({ type: "js" });

Your problem is that positiveChart is not in the scope of your other functions because you declare it inside makeChart. In order to fix that you must have it in the react useState like this:

react-tooltip doesn't support components as the tooltip content, but accepts html strings.

1. You should use the data-html={true} prop to let the react-tooltip know that the value passed to data-tip is actually an HTML code.

2. Then you should provide the html of the tooltip content as a string.

So this should work:

I had this problem today and did npm install eslint-config-react-app like on github is recommended. After that console adviced me to install @babel/core and typescript, so i installed them by npm install @babel/core and npm install typescript

I'm a bit surprised you're loading types from the types.d file direct and with a build path! I'd expect rather import { Type } from '@myorg/component-library.

That's because as part of creating the package.json for a typescript-authored npm library you'd be defining a main property pointing to the place that exports all the Javascript properties and a types property pointing to the place that exports the typescript types you want.

If that main entry point (because of your build process) is actually build/index.js and the corresponding types file is build/index.d.ts then you'd never directly reference the build folder or files when importing - pointing to the right path is dealt with by the bundling process.

Take a look at a mainstream (but simple) typescript npm module like https://github.com/jamiebuilds/unstated-next/blob/master/package.json ( https://www.npmjs.com/package/unstated-next )

You can see the main property pointing to the file which should export the javascript names https://github.com/jamiebuilds/unstated-next/blob/master/package.json#L6 and the types property pointing to the file which should export the types https://github.com/jamiebuilds/unstated-next/blob/master/package.json#L9 and these happen to be in the 'dist' folder but this is never referenced when importing it as per the docs at https://www.npmjs.com/package/unstated-next