Jeremy Walker

Seems like it would be a lot simpler to instead have: ``` const asyncSum = await urls.asyncReduce(async (sum, url) => { const response = await fetch(url); const { number }...

*EDITED* I was running it in the parent folder again. When I ran it in the sub-folder, it worked! Thanks.

Ah, that's the problem: I downloaded from https://jqueryui.com/. Thanks. While that's definitely my fault for not reading the instructions, at the same time it seems like a mistake a lot...

For what it's worth, I'm not sure that is a correct impression. Developers using AMD are almost exclusively using Require.js ... which is to say they're one step up from...

@ralfstx I agree that it would be better for the plug-in to "just work", with a *.js pattern, rather than requiring configuration initially. If both Sam and I missed that...

>this setting manages that case template-string-converter.convertWithinTemplateString As an aside, it's strange that that setting isn't turned on by default: I can't imagine anyone wanting: $('div[data-testId="foo"]') to become: $('div[data-testId=`${foo}`]') *Everyone* would...

Just one more "me too" vote. Virtually every other test runner/assertion library provides a way to supply a custom assertion message. For instance, here's how they do it in [Jest](https://stackoverflow.com/questions/45348083/how-to-add-custom-message-to-jest-expect),...

No apology needed, I was just trying to determine the project's status! In all honesty though, since it seemed dead I just went with another project.

I wound up making my own with Next.js and Postgraphile, but there are lots of headless CMS projects out there.

Agreed! `ownProperties` is an incredibly wonky name. It _does_ solve a very niche concern (although, with OOP declining in popularity in JS, how many devs even know about the prototype...