Michał Gołębiowski-Owczarek

Thanks for the report. FWIW, you wouldn't ever need: ```js import jQuery from './node_modules/jquery/dist/jquery-esm.js'; ``` In fact, it could be quite fragile as npm dependencies may be hoisted. This is...

Ah, right, I was thinking about a bundler use case and you mean native browser import, got it. If there's no need for bundling then we could just point to...

jQuery already has a build process based on Rollup defined in https://github.com/jquery/jquery/blob/master/build/tasks/build.js. For now it only generates a regular script file & its minified version; this could be enhanced to...

> @mgol generally the ESM version would only be used by bundlers right? Not only. Node.js has experimental ESM support, docs at https://nodejs.org/api/esm.html; it'd be good to work good with...

@brettz9 This past comment of mine in this thread is still relevant: https://github.com/jquery/jquery/issues/4592#issuecomment-607359647. In particular, its second section. If we want to generate an ESM file, we'd probably also need...

I've added the `Blocker` label to it since adding `exports` is a breaking change so we need to do it in 4.0.0.

Maybe not using the `url()` wrapper would help? In any case, it looks like a tooling issue and seeing jQuery UI 1.12.1 is identical here, given limited team resources it's...

These are browser interventions that limit features of some events in exchange of performance. This is not really related to jQuery or jQuery UI but how you use them. Except...

Closing because of a lack of response. We can reopen if needed info is provided.

I agree with @gibson042, we should try to align with the spec as much as possible, cutting corners only where the browser APIs are clumsy.