1.3.2.2 contains two jquery versions

[mxab]

Hi,

I created a fresh project and added jquery via npm and use it via import jQuery from 'jquery'.

The application has still the packages/jquery.js (1.11.2) but also in the modules.js the npm jquery version

See this basic project sample
https://github.com/mxab/meteor-jquery-issue

[Ben305]

You have to remove the meteor package for jquery. This is still included in your sample.

[mxab]

@Ben305 I thought the idea of the 1.3.2 release was that it would then take the jQuery provided by the node modules. Also removing jquery from packages does not show any effect, I assume to some transitive dependency in in some other meteor package.

[abernix]

At the moment blaze-html-templates requires jquery itself. Thus if you continue to use blaze-html-templates (or any other private/public package that uses jquery using the Atmosphere system) this will continue.

With your example, if you remove jquery and blaze-html-templates with meteor remove, you should see the second version go away.

I know there are efforts under way to fix this in Blaze, but don't remember where the ticket is right now (If you want to peek around, Blaze progress is happening over in https://github.com/meteor/blaze now)

[mxab]

@abernix have you seen this issue #6626 ? As far as I get it the meteor jquery package should detect jquery in the node modules and does not load the built in version, shouldn't it?

[bySabi]

You can make the trick creating a local 'jquery' that import already installed jquery module. For example: https://github.com/bySabi/neal-sample-meteor/tree/master/packages/meteor-jquery--module

Remember update version on meteor release updates.

Current version is: 1.11.8

[abernix]

If you install your own version of jQuery with NPM, it should be used. If you don't find this to be the case, please reproduce in the latest version of Meteor and upload a reproduction repo to Github and provide the link.

Thanks!

#7202 (related)

[coagmano]

Even though meteor/jquery does use the npm version when one exists, it still sends it's version to the client in the initial bundle, without using any of the code.

Is there a way to stop meteor from bundling version 1.11.2 to the browser when an npm version exists?

Can dynamic imports help here?