Skip to content
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

Release a new version with changes since 0.17 ? #666

Closed
jdeniau opened this issue Jan 2, 2018 · 4 comments
Closed

Release a new version with changes since 0.17 ? #666

jdeniau opened this issue Jan 2, 2018 · 4 comments

Comments

@jdeniau
Copy link
Contributor

jdeniau commented Jan 2, 2018

Hi,

Is it possible to release a new version with all changes since 0.17 ?

There are quite a few improvements that can not be used for now. 😿

Thank you !

@tobiasandersen
Copy link
Collaborator

There's nothing stopping you from using those new features. I'm sure there'll be a new release when Jason has the time and energy and feels like the time is right.

Personally I never appreciate "issues" like these, since the only thing they can possibly achieve is to put pressure and add more stress on the maintainer. Please understand it's currently also a holiday for a lot of people.

@jdeniau
Copy link
Contributor Author

jdeniau commented Jan 4, 2018 via email

@wasabigeek
Copy link

wasabigeek commented Jan 12, 2018

Hi @tobiasandersen, genuine noob question here - when you say nothing is stopping us from using the new features, you mean we need to fork/download and build ourselves? I tried to do npm install --save intljusticemission/react-big-calendar#0b2c2347efa8fe4fb77f7931634de9a8ee1362ac (locked at a commit in an attempt to have a deterministic build), but that doesn't include the lib or src folder.

@tobiasandersen
Copy link
Collaborator

Forking and building yourself is definitely an option (maybe the easiest even). If you npm install like you did, you should get the src folder (are you sure it's not there?). The problem is that it's looking for lib/index.js, and the lib folder won't be there. You could work around that a few different ways (e.g. forking and changing it to look for src/index.js, or make an alias in webpack). You'd also have to setup the build steps required in your own config if you use the src files. There might be other ways as well that I don't know of.

I believe there're still some problems on master, and #578 is about to get merged. But once that's done and master looks alright, I think a new release would make a lot of sense.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants