Here is a minimal repro: https://github.com/hluz/dyld
By default in package.json dependencies is existing package - meteor-node-stubs. Do we need this package?
Just a note for anyone upgrading to the 1.3 version for the first time; on my (Windows) machine it took 21 minutes for everything to download and update after typing meteor update --release 1.3-rc.3
, so donāt be alarmed if it appears to have got stuck.
Hmmm⦠Iām seeing really long rebuild times on rc3 on Windows.
On beta.12 my app takes 6 seconds from saving a change to the browser finishing updating. Once I install rc3 that jumps to 42 seconds. Anybody else experiencing this?
Hi, ffxsam I am using 1.3 rc 3 with no issues other then this "Cannot find module āutilā when I try to use temboo npm module. Any ideas?
Thanks
Itās definitely a problem with the activedirectory package. Or it just doesnāt play nice with Meteor. I had this problem with aws-sdk and stripe previously, too (the Meteor team had to fix something).
If you can verify that the package works totally fine without Meteor, Iād maybe report it as an issue.
Solved, I had it in the client folder. Node Https and util run on the server only.
Thanks
1.3-rc.3 works great for me! I only have problems deploying with mup (see https://github.com/arunoda/meteor-up/issues/915), but itās unclear if that has anything to do with the new Meteor release.
Love the module support! SCSS modular support in 1.4 would be awesome
Resolved. It appears to be a npm version issue. Using meteor npm install
instead of npm install
fixes the problem.
Oh, interesting. Iāll keep that in mind if I run into any issues in the future.
Any input on meteor-node-stubs, its use case scenarios
Node (on the server) provides a lot of built-in modules like process
, path
, http
etc. Obviously these donāt exist in the browser, so packagers like webpack and browserify automatically include client-side implementations.
Various npm packages have become dependent on this kind of environment, and as such, did not work initially with Meteor. But now Meteor does the same thing since beta.12
, and theyāre mapped in via this package.
Thanks, now I get it.
Is the any reason why it is not meteor package?
Er, āmeteor npm installā doesnāt get any useful hits on Google. Is that the way we should install all NPM packages in 1.3 now? Because Iāve just been using npm install (so far without issue).
meteor npm
was only recently added, and all it does is call into the version of NPM bundled with Meteor. There is no need to use it if you have an existing installation of NPM that works, but it is meant as a convenience for people who donāt have it installed yet.
In case someone finds themselves here and is looking for updated release candidate info, the latest version is 1.3-rc.10
To update to the latest release candidate, run the following command in your meteor project:
meteor update --release 1.3-rc.10
If you want to stay on top of the release candidate action, hereās the url: https://github.com/meteor/meteor/issues/6266
Something to keep in mind for people jumping from one RC to the next: keep an eye on your ~/.meteor
folder (the one in your home folder). Every time you use a different version of Meteor, different package versions are pulled, and that directory can become massive (mine was 14GB).
Once things settle and 1.3 is released, it might be wise to do an rm -rf ~/.meteor
to start fresh. (EDIT: see Benās post below, actually)
You can reclaim most of that space without having to re-download the package catalog (~/.meteor/package-metadata
) if you just rm -rf ~/.meteor/packages
:
% du -chs ~/.meteor/*
4.0K /Users/ben/.meteor/meteor
204M /Users/ben/.meteor/package-metadata
4.9G /Users/ben/.meteor/packages
5.1G total
@benjamn thanks for the useful snippet. Is there anything we should be cautious about when deleting the /.meteor/packages
directory?
@pronevich yes! We chose to make meteor-node-stubs
an npm package instead of a core Meteor package primarily so that we can iterate on it independently from the Meteor release cycle. Feel free to file issues and submit pull requests here!