Granze / react-starterify

A minimal React JS application starter kit
http://granze.github.io/react-starterify/
665 stars 71 forks source link

State is undefined when compiled into production, but works fine when in development #41

Closed komocode closed 8 years ago

komocode commented 8 years ago

In my render(), I have this

//....
<div className="form-group">
                        <label>ADDRESS</label>
                        <input className="form-control" disabled placeholder="" value={this.props.workshop.store.address} />
                    </div>
            <div className="form-group">
              <ViewMap
                name={this.props.workshop.store.doorName}
                lat={this.props.workshop.store.lat}
                lng={this.props.workshop.store.lng}
              />
            </div>
//....

this.props.workshop is defined in development, but when I compile and push to production, this.props.workshop is undefined.

I have mirrored my MySQL database from production so that I have the EXACT same data running locally. There shouldn't be any difference between the two, but yet I'm pulling my hair out to figure out why it's only undefined in production.

FYI: Production files are on AWS S3 while development is happening on my local machine.

komocode commented 8 years ago

Nevermind, not an issue with react-starterify's build process. It was Cloudflare's CDN causing some weird caching issues.