Meteor 1.3 *early beta* now available

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.

1 Like

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 Like

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 :smiley:

1 Like

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.

See https://github.com/meteor/meteor/issues/6056.

2 Likes

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.

6 Likes

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)

4 Likes

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
6 Likes

@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!

1 Like