You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of the big arguments against adopting this library is that it has "less eyes" on it
I see that you have invested a lot of work into converting the original library to ES6 however it is not trivial to "rebase" this fork on changes upstream.
My suggestion is to split the conversion process into two distinct steps that will enable easier rebasing:
Move all code that does not change from inside the existing source files to other files, agnostic of the module system.
Complete the migration to ES6 based on that.
Does that sound feasible?
The text was updated successfully, but these errors were encountered:
One of the big arguments against adopting this library is that it has "less eyes" on it
I see that you have invested a lot of work into converting the original library to ES6 however it is not trivial to "rebase" this fork on changes upstream.
My suggestion is to split the conversion process into two distinct steps that will enable easier rebasing:
Does that sound feasible?
The text was updated successfully, but these errors were encountered: