Unleash / unleash-proxy-client-js

A browser client that can be used together with the unleash-proxy.
Apache License 2.0
44 stars 46 forks source link

Failed to parse source map Warning #178

Closed sriadimanav closed 8 months ago

sriadimanav commented 8 months ago

Describe the bug

package version: 3.1.0 react version: 18.2.0 react scripts version: 5.0.1

Getting warnings in console after upgrading to latest version

Steps to reproduce the bug

install latest version using yarn

Expected behavior

should not throw warnings

Logs, error output, etc.

No response

Screenshots

image

Additional context

No response

Unleash version

3.1.0

Subscription type

None

Hosting type

None

SDK information (language and version)

No response

sjaanus commented 8 months ago

Hey @sriadimanav! 😊 To better assist you, could you let me know which node version you're using? Also, did v3.0.0 work properly for you?

Currently was not able to reproduce by this. This gives the same versions you described.

npx create-react-app react-app
cd react-app
yarn install

Do you have anything else added that could cause this?

Tymek commented 8 months ago

I was able to reproduce it with create-react-app Typescript template. Related to cra discussion: https://github.com/facebook/create-react-app/discussions/11767 Looks unrelated to Unleash. See https://github.com/facebook/create-react-app/pull/11752

Tymek commented 8 months ago

After further investigation, maybe I'll be able to do something about this.

https://sourcemaps.io/report/1698835631581_https%3A%2F%2Funpkg.com%2Funleash-proxy-client%403.0.0%2Fbuild%2Fmain.esm.js

Tymek commented 8 months ago

Fixed in v3.1.1

CC @sriadimanav

sriadimanav commented 8 months ago

Hey @sriadimanav! 😊 To better assist you, could you let me know which node version you're using? Also, did v3.0.0 work properly for you?

Currently was not able to reproduce by this. This gives the same versions you described.

npx create-react-app react-app
cd react-app
yarn install

Do you have anything else added that could cause this?

Node version: 20.8.0

sriadimanav commented 8 months ago

Fixed in v3.1.1

CC @sriadimanav

thanks @Tymek