React-slick: errors in concurrent mode - > UNSAFE_componentWillMount

[pejman1]

index.js:14426 Warning: Using UNSAFE_componentWillMount in strict mode is not recommended and may indicate bugs in your code. See https://fb.me/react-unsafe-component-lifecycles for details.

• Move code with side effects to componentDidMount, and set initial state in the constructor.

Please update the following components: InnerSlider, Slider

index.js:14426 Warning: Using UNSAFE_componentWillReceiveProps in strict mode is not recommended and may indicate bugs in your code. See https://fb.me/react-unsafe-component-lifecycles for details.

• Move data fetching code or side effects to componentDidUpdate.
• If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://fb.me/react-derived-state

Please update the following components: InnerSlider

[smorfe]

I am having the same issue...

[paufar]

same here would be good if this gets updated

[Aristod3mus]

same problem

[moh3ni]

same issue

[bijaybdrkarki]

@akiran can you please have a look at the issue..?

[olasunkanmi04]

I have the same issue

[Jeconias]

Same issue

[imparvez]

@akiran facing the same issue. Can you please look into this issue and if any changes, then when are you planning to take it? Thanks

[tuguldur]

ReactDOM.render(
  <React.StrictMode> 
    <App />
  </React.StrictMode>,
  document.getElementById("root")
);

to

ReactDOM.render(
    <App />,
  document.getElementById("root")
);

[pejman1]

ReactDOM.render(
  <React.StrictMode> 
    <App />
  </React.StrictMode>,
  document.getElementById("root")
);

to

ReactDOM.render(
    <App />,
  document.getElementById("root")
);

It doesn't solve the problem

[bijaybdrkarki]

ReactDOM.render(
  <React.StrictMode> 
    <App />
  </React.StrictMode>,
  document.getElementById("root")
);

to

ReactDOM.render(
    <App />,
  document.getElementById("root")
);

for me it solved the problem. thanks

https://reactjs.org/docs/strict-mode.html

[olasunkanmi04]

ReactDOM.render(
  <React.StrictMode> 
    <App />
  </React.StrictMode>,
  document.getElementById("root")
);

to

ReactDOM.render(
    <App />,
  document.getElementById("root")
);

This solved it for me. Thank you

[pejman1]

ReactDOM.render(
  <React.StrictMode> 
    <App />
  </React.StrictMode>,
  document.getElementById("root")
);

to

ReactDOM.render(
    <App />,
  document.getElementById("root")
);

This solved it for me. Thank you

interesting ! for me the error is still there

Warning: Using UNSAFE_componentWillMount in strict mode is not recommended and may indicate bugs in your code. See https://fb.me/react-unsafe-component-lifecycles for details.

• Move code with side effects to componentDidMount, and set initial state in the constructor.

Please update the following components: InnerSlider, Slider
index.js:16181 Warning: Using UNSAFE_componentWillReceiveProps in strict mode is not recommended and may indicate bugs in your code. See https://fb.me/react-unsafe-component-lifecycles for details.

[paufar]

@akiran do you think you will fix this issue please?

[ajj-siraj]

ReactDOM.render(
  <React.StrictMode> 
    <App />
  </React.StrictMode>,
  document.getElementById("root")
);

to

ReactDOM.render(
    <App />,
  document.getElementById("root")
);

This works but you're not changing anything except removing the error message and all the benefits of the strict mode.
The comp still needs to be updated.

[mactung]

i have problem too anyone can fix it

[Alekseyideas]

i have problem too anyone can fix it

delete until they update react-slick with fixes

[RomanistHere]

How could this be most popular library for react and you have to disable strict mode to run it?

[andocodes]

Following this. It's not a complete gamebreaking change but would be nice to get rid of this. Looks like we need to swap out the unsafe React methods. @akiran thoughts/how far have we got with this?

[akiran]

@andocodes I am working on it. Hopefully, I will make a release next week with a fix for this

[akiran]

@andocodes @Alekseyideas @mactung @paufar @pejman1 @smorfe @moh3ni
I release [email protected] with a fix for this.

Can you test it now?

[paufar]

@akiran Confirmed from my end! Error is gone. Thankyou!

[andocodes]

@akiran just to also confirm - all gone now. Awesome work bud!