-
Notifications
You must be signed in to change notification settings - Fork 164
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fail to minify into react-create-app #55
Comments
Hi, This is due to the minify engine. Regards |
HI, Regards |
For information on my side I use |
Have same issue es6 but need es5 when making production build. Perhaps a es5 version would be accommodating for some of us. |
Hi, don't hesitate to modify package.browsers rule and compile it using gulp to get a ES5 working version ;-) |
🎉 This issue has been resolved in version 0.3.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
I rewrote this lib from the ground up for use in React, leveraging his great SASS styling, but made specifically for React. I've open-sourced the code here: Note that my implementation uses my Dialog as a Promise component, which is also open-source (and linked to). You can use that also if you like. But if you don't, you're free to modify DatePicker.js to use whatever methodology you prefer. This is why I haven't turned it into standalone "npm install" library. Hope you find it useful! |
Would be awesome to get a React component up on npm for this! |
Hi,
congratulations for your job with Bulma-Calendar component, it's great!
I have an issue with react-create-app build and bulma-calendar library.
I import it in this way
and it works correctly on development environment (npm run start or react-scripts start).
But if I try to make a build of the application (npm run build or react-scripts build), the build process return this error:
In that link is reported:
To resolve this: Open an issue on the dependency's issue tracker and ask that the package be published pre-compiled. Note: Create React App can consume both CommonJS and ES modules. For Node.js compatibility, it is recommended that the main entry point is CommonJS. However, they can optionally provide an ES module entry point with the module field in package.json. Note that even if a library provides an ES Modules version, it should still precompile other ES6 features to ES5 if it intends to support older browsers.
Can we do anything to resolve it?
Thanks
Aurelio
The text was updated successfully, but these errors were encountered: