-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Promise returned by render has or has not .done()
method, depending on environment.
#2446
Comments
I don't want to have to always use a dependency just for one function. If the done function becomes standard we can test for it in the native implementation and then decide which version to use. Other team members might disagree so I'm leaving this NeedsDecision |
@lukeapage npm will always (at least try to) download then/promise, so if it is there you might as well always use it. |
Yes ive considered that (changing to pure shim) and its maybe what we
should do. Actually alot of people install less with no optional option to
npm which does not include optional deps.
|
I think |
Only if you dont pass in a callback. I was using promises internally but
then its forced async callback interfered with our sync option, which seems
to be used alot in browser and node environments where for some reasons its
not practical to be async :(
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Less.js is using then/promise as shim for Promise if it is not provided by environment. However, promises as created by then/promise have non-standard (but very useful!)
.done()
method while native ones do not. Which leads to inconsistency.Related: gulp-community/gulp-less#140 -
render().done()
is not a function, but only with modern v8.The text was updated successfully, but these errors were encountered: