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
In 4.x, the build process was deprecated. In 5.x, I'd like to see it removed.
I know this is going to cause problems for some users (that are mis-using debug or mis-using version ranges), but I'm hoping the legacy users that still rely on debug@* (seriously, stahp doing that...) were fixed up a bit after the release of 4.x since it introduced enough breaking changes to get that ball rolling.
Ultimately, debug is not a complicated package. It's not a package that warrants the use of splat-property-functional-ternary-resolvers or whatever new crazy ecmascript proposal came out last week.
You get an extra big header because I know the majority of angry people will be browser users 🙃
I see you. However, with the current state of Javascript and frontend development, Babelification has become a part of life.
If you want to see the current position regarding ES5 bundling and whatnot, please see Sindre Sorhus's wonderful writeup at this link: sindresorhus/ama#446 (comment)
The only subtle difference is that debug was originally intended to be both Node.js and first-class browser compatible. I intend to keep it that way, with a few changes with where each of these implementations live (see #556).
I ultimately want to get rid of this weird, uncertain split of functionality entirely as it causes endless build problems and questions and assumptions and issues and etc.
While this ticket is relatively small and actionable, please see #556 and #644 for more context as to what changes to expect in 5.x. It's still not entirely certain the landscape of user experience, however...
... that's why several of the open issues are still RFCs and I urge everyone to contribute to them as I would love to hear feedback.
The text was updated successfully, but these errors were encountered:
In 4.x, the build process was deprecated. In 5.x, I'd like to see it removed.
I know this is going to cause problems for some users (that are mis-using
debug
or mis-using version ranges), but I'm hoping the legacy users that still rely ondebug@*
(seriously, stahp doing that...) were fixed up a bit after the release of 4.x since it introduced enough breaking changes to get that ball rolling.Ultimately,
debug
is not a complicated package. It's not a package that warrants the use of splat-property-functional-ternary-resolvers or whatever new crazy ecmascript proposal came out last week.We should be supporting the language features supported by the latest LTS Node (at the time of this writing, it's currently 8.x and will soon be 10.x with the new year) and nothing newer.
Browser Users
You get an extra big header because I know the majority of angry people will be browser users 🙃
I see you. However, with the current state of Javascript and frontend development, Babelification has become a part of life.
If you want to see the current position regarding ES5 bundling and whatnot, please see Sindre Sorhus's wonderful writeup at this link: sindresorhus/ama#446 (comment)
The only subtle difference is that
debug
was originally intended to be both Node.js and first-class browser compatible. I intend to keep it that way, with a few changes with where each of these implementations live (see #556).I ultimately want to get rid of this weird, uncertain split of functionality entirely as it causes endless build problems and questions and assumptions and issues and etc.
While this ticket is relatively small and actionable, please see #556 and #644 for more context as to what changes to expect in 5.x. It's still not entirely certain the landscape of user experience, however...
... that's why several of the open issues are still RFCs and I urge everyone to contribute to them as I would love to hear feedback.
The text was updated successfully, but these errors were encountered: