Newbie Question: Cannot find module 'meteor/std:accounts-ui'? about accounts-ui

[queso]

I feel like this is a core Meteor issue and likely not anything you are doing... Perhaps time to ping @tmesday or @benjamn?

[xavxyz]

@queso solved it live just few minutes ago cloning the package repo (this one) directly into the packages folder of the app.

I tried this way of doing on an app of mine too, no more problems with dependencies! Everything runs fine! That's a way to handle it by now 💯

[timbrandin]

I guess we can close then.

[tjramage]

@PolGuixe – I agree! I've just updated to 1.1.19 and latest tracker-component and still seeing the same issue.

[timbrandin]

Yeah, seems like it works better for me on a clean app installation, anyone want to check out the devel version I've pushed, you could just clone it into /packages and checkout devel to try it out.

[raphaelkross]

@SachaG - perhaps deleting the node_modules, checking the versions at package.json and running npm install again remove any cache problem.

[VikR0001]

Interesting. Via the console, I see that std_accounts-ui is loading. I have a breakpoint set on line 25148, and execution is halting at that breakpoint:

Line 25148: require("./node_modules/meteor/std:accounts-ui/check-npm.js");

Now here's the odd thing. That line is looking for the package at

./node_modules/meteor/std:accounts-ui

But it isn't installed there. In fact, there is no folder called "meteor" in my node_modules folder. std_accounts-ui is currently installed at

myApp/.meteor/local/build/programs/web.browser/packages/std_accounts-ui.js

How can I install std:accounts-ui in the place where it expects itself to be?

[timbrandin]

What version of Meteor are you on? So that I can try to reproduce it during the day or this week.

[PolGuixe]

I am getting the same as in #29

You can reproduce it here: https://github.com/Zetoff/trajectory/tree/meteor-and-packages-update

[VikR1000]

@timbrandin, I am in Meteor 1.3.1.

[tjramage]

I'm also having this issue since updating to 1.3.1.

[timbrandin]

@VikR0001 alright, thx.

[PolGuixe]

In my case is independent from the Meteor version -1.3 or 1.3.1- , but since the std:accounts-ui was updated to 1.1.14.
std:[email protected] works fine.

[timbrandin]

Ok, so I'll see with what those two versions differ.

[raphaelkross]

@timbrandin Also experiencing this issue - so I'll be waiting for more informations or even better, a fix!

Thank you!

[PolGuixe]

@timbrandin I don't think that cloning the package to the /packages folder is a legit solution.

[PolGuixe]

This is difficult to debug it myself since, if I clone the package to /packages then the error disappears.
Is there any way we can help?

[benjamn]

The errors about missing <npm-package>/package.json files are due to this code checking for packages that are never otherwise imported in this package or the app. When you don't import a package on the client, it doesn't get bundled into your app at all—hence the missing module errors!

You can make those errors go away by putting

import "react";
import "react-dom";
import "tracker-component";

anywhere in your client code. I'm tempted to say std:accounts-ui shouldn't be checking those packages unless it imports them, but I suppose there may have been a good reason to check.

@tmeasday Perhaps the absence of a package.json file should be a sign that the package is never used, and therefore its version doesn't matter?

[tmeasday]

So this issue was partly caused by an error in check-npm-versions' detection of missing modules on the client (fixed by Meteor-Community-Packages/check-npm-versions@f50c986, @benjamn what do you think about my janky string matching; do you have a better idea?)

If you update to tmeasday:[email protected] you should see a more informative error message (although maybe it's not that much more useful).

Ultimately though @benjamn is right, the package should import the things it's checking I suspect.

[tmeasday]

Perhaps the absence of a package.json file should be a sign that the package is never used, and therefore its version doesn't matter?

I'm not sure this makes sense; what if the user has legitimately forgotten to install the npm package? How can we distinguish on the client?

[SachaG]

Running into the same issue, I'll downgrade back to 1.1.12 for now.

[timbrandin]

I'm not sure how to handle this @SachaG, would it work better without tmeasday:check-npm-versions?

[timbrandin]

Btw @benjamn I've noticed that if you update a local package in for example another folder, the .meteor/local built package inside the app doesn't update and get the new node_modules if they where updated, is that a bug with meteor?

[SachaG]

@timbrandin I guess? I'm not super clear on what's causing the issue but we can probably not use that package for now?

[PolGuixe]

Release 1.1.20 seems to be working fine.

Great job!

[timbrandin]

Awesome. I'll close this then.

[SachaG]

Has this issue actually been fixed? I was using 1.2.6 and just ran into it again.

[limratana]

I came across this issue and benjamn's solution seems to have solved the problem for me.

I am still hitting this issue. @benjamn importing tracker-component into my ui code doesn't seem to help :(