problems on "Backend" about react-id-swiper HOT 5 CLOSED

For whoever googling this: Swiper library is lame not supporting server-side at all (and the author is ignorant).
Still there is a hacky workaround: nolimits4web/swiper#1541 (comment)

from react-id-swiper.

a first workaround:
module.exports = factory( require('react'), require('react-dom'), !!((typeof window !== 'undefined' && window.document && window.document.createElement)) ? require('swiper'): null, require('object-assign') );

from react-id-swiper.

Hi @crazyx13th , here is a solution we already discussed #14 .

from react-id-swiper.

@kidjp85 if the main Swiper works fine with React (nolimits4web/swiper#1541 (comment)) does react-id-swiper offer any benefits?

from react-id-swiper.

<Swiper> original component can be wrapped to fix it for the server side:

import React, { Component } from 'react'

// https://github.com/nolimits4web/Swiper/issues/1541#issuecomment-271439046
export default class FixedSlider extends Component {
  state = {}

  componentDidMount() {
    this.setState({
      Swiper: require('react-id-swiper')
    })
  }

  render() {
    const { Swiper } = this.state

    if (!Swiper) {
      return null
    }

    return <Swiper {...this.props}>{this.props.children}</Swiper>
  }
}

from react-id-swiper.