Please help test the latest 1.3.3 beta release!

vikti · June 4, 2016, 4:04pm

I have also a problem with class-property-transform.

At build time this:

...

class DetailsContainer extends React.Component{

  @observable loaded = false; //<---- this causes the error
  entity = {};

...

throws this error:

=> Errors prevented startup:                  
   
   While building for web.browser:
   imports/common/ui/organisms/BrowserEntities/containers/DetailsContainer.jsx:19:14:
   /imports/common/ui/organisms/BrowserEntities/containers/DetailsContainer.jsx: Missing class
   properties transform.

Here is my .babelrc:

{
  "presets": [
    "meteor",
    "stage-0"
  ],
  "plugins": [
    "transform-decorators-legacy",
    "transform-class-properties"
  ]
}

and my package.json:

{
  "private": "true",
  "scripts": {
    "start": "meteor run"
  },
  "dependencies": {
    "meteor-node-stubs": "~0.2.0",
    "mobx": "^2.1.3",
    "mobx-react": "^3.0.4",
    "react": "^15.0.1",
    "react-dom": "^15.0.1",
    "react-router": "^2.2.4",
  },
  "devDependencies": {
    "babel-plugin-transform-class-properties": "^6.9.1",
    "babel-plugin-transform-decorators": "^6.8.0",
    "babel-plugin-transform-decorators-legacy": "^1.3.4",
    "babel-preset-decorators-legacy": "^1.0.0",
    "babel-preset-meteor": "^6.9.0",
    "babel-preset-stage-0": "^6.5.0",
    "babel-preset-stage-1": "^6.5.0",
    "babel-runtime": "^6.9.2"
  }
}

Note I am using typescript (out of react). Here is my installed package:


meteor-base             # Packages every Meteor app needs to have
mobile-experience       # Packages for a great mobile UX
mongo                   # The database Meteor supports right now
blaze-html-templates    # Compile .html files into Meteor Blaze views
reactive-var            # Reactive variable for tracker
jquery                  # Helpful client-side library
tracker                 # Meteor's client-side reactive programming library

standard-minifier-css   # CSS minifier run for production mode
standard-minifier-js    # JS minifier run for production mode
es5-shim                # ECMAScript 5 compatibility for older browsers.
ecmascript              # Enable ECMAScript2015+ syntax in app code

barbatus:typescript
accounts-base
#gadicc:ecmascript-babelrc
accounts-ui
accounts-password
random
ground:db@2.0.0-rc.3

nbrady · June 4, 2016, 6:47pm

You shouldn’t need any of the presets, so remove them from the .babelrc. Delete your node_modules directory and reinstall your node packages. This solved the problem for me.

reoh · June 4, 2016, 8:28pm

& make sure there’s no other .babelrc files in your project which might be overriding the root file

vikti · June 4, 2016, 8:37pm

Thx @nbrady @reoh, but sorry, it does not change anything. Is there something wrong in my dev dependencies? I don’t really know what I am doing with babel. I need to use arrow function, class props and decorator. Does the “stage thing” is necessary?

reoh · June 4, 2016, 8:48pm

Probably not. Try uninstalling or removing:

"babel-preset-meteor": "^6.9.0",
"babel-preset-stage-0": "^6.5.0",
"babel-preset-stage-1": "^6.5.0",

from the package.json, then

npm prune

to remove unused dependencies

vikti · June 4, 2016, 8:51pm

even meteor preset?
I understood that is necessary for react and es2015:

But when @benjamn says it is always included, maybe he means it is already included in the meteor release?

benjamn · June 4, 2016, 8:54pm

That’s right, babel-preset-meteor comes from meteor-babel which is an Npm.depends-style dependency of the babel-compiler package, so you don’t need to worry about installing babel-preset-meteor or putting it in your .babelrc file.

Also you might as well meteor update --release 1.3.3-rc.0 now, just in case that helps.

nbrady · June 4, 2016, 9:00pm

@benjamn How can we easily track when the rc’s are available? I’m using 1.3.3-beta.1 until I saw your post here. It would be cool if there were some setting, especially when running meteor in beta that would tell us that the rc is available. (And in the rc when the actual release is available)

benjamn · June 4, 2016, 9:13pm

At the moment, https://github.com/meteor/meteor/releases is your best bet, though I would make sure the release is at least an hour old before you try updating, since it shows up in that list before I’ve finished publishing meteor-tool.

vikti · June 4, 2016, 9:15pm

haaa thx a lot, the rc.0 did the work! Thx you so much!

trajano · June 5, 2016, 7:03pm

Would this update work on Windows? I just tried it now and it’s just taking a long while to “download” and ends up with this

D:\p\meteor-boilerplate>meteor update --release 1.3.3-rc.0
=> Errors while initializing project:

While loading package npm-bcrypt@0.8.5:
error: Command failed: gyp
npm ERR! Windows_NT 10.0.14352
npm ERR! argv
"C:\\Users\\Archimedes\\AppData\\Local\\.meteor\\packages\\meteor-tool\\1.3.3-rc.0\\mt-os.windows.x86_32\\dev_bundle\\bi
n\\\\node.exe"
"C:\\Users\\Archimedes\\AppData\\Local\\.meteor\\packages\\meteor-tool\\1.3.3-rc.0\\mt-os.windows.x86_32\\dev_bundle\\li
b\\node_modules\\npm\\bin\\npm-cli.js"
"rebuild"
npm ERR! node v0.10.45
npm ERR! npm  v2.15.1
npm ERR! code ELIFECYCLE
npm ERR! bcrypt@0.8.5 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the bcrypt@0.8.5 install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the bcrypt package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs bcrypt
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!
npm ERR!     npm owner ls bcrypt
npm ERR! There is likely additional logging output above.

Alameli · June 6, 2016, 4:06am

Hi Trajano,

I got the same issue after updating meteor to that release you mentioned but I fixed it by installing the Visual C++ build tools

http://go.microsoft.com/fwlink/?LinkId=691126

Got the hint from here:

jesperwe · June 6, 2016, 6:45am

So I have a fairly large app that I got upgraded to beta.2 without much effort.
But with rc.0 it falls apart completely

It starts with Uncaught ReferenceError: meteorBabelHelpers is not defined and then lots of weird errors from misc packages.

Downgrading again to beta.2 it works fine.

jesperwe · June 7, 2016, 11:07am

More info on my comment above:

App still fails at 1.3.3-rc.1, still works when downgrading to 1.3.3-beta.2.

The exact error is:

Uncaught ReferenceError: meteorBabelHelpers is not defined
    extend @ peerlibrary_blaze-components.js?hash=d9f1367…:1139
    (anonymous function) @ peerlibrary_blaze-components.js?hash=d9f1367…:1681
    (anonymous function) @ peerlibrary_blaze-components.js?hash=d9f1367…:2367
    (anonymous function) @ peerlibrary_blaze-components.js?hash=d9f1367…:2426
    (anonymous function) @ client.coffee:103

@mitar, @benjamn: Not sure if I should report this as a Meteor or a BlazeComponents issue?

mitar · June 7, 2016, 11:20am

Seems like regression in Meteor.

rlespagnol · June 7, 2016, 11:41am

@trajano I have the same error with beta2…

awatson1978 · June 7, 2016, 1:46pm

I got practicalmeteor:mocha-console-runner working! next step is to integrate with spacejam and get CI working, and then Istanbul integration working.

jesperwe · June 7, 2016, 2:08pm

Ok, submitted #7184.

benjamn · June 7, 2016, 8:09pm

New release: 1.3.3-rc.4

To update to the latest release candidate of Meteor 1.3.3, run

meteor update --release 1.3.3-rc.4

in an application directory.

Changes.

birk · June 10, 2016, 10:19pm

I haven’t tried the beta nor rc, but I updating to the 2h new 1.3.3 release from 1.3.2.4.

I expected the meteor node and meteor npm version to be updated to v0.10.45 and 2.15.1 as it says in the History.md, but they stayed on v0.10.43 and 2.14.22.

Are they supposed to do that?