Meteor app crashes during start-up

[rohanray]

trafficstars

Hi,

Glad to see you working on mixing meteor and polymer. I created a new meteor app and installed your package. However, the app crashes with the following error message:

W20150608-21:47:40.718(1)? (STDERR) TypeError: Arguments to path.resolve must be strings W20150608-21:47:40.722(1)? (STDERR) at Object.exports.resolve (path.js:116:1 5) W20150608-21:47:40.722(1)? (STDERR) at Object.exports.relative (path.js:240: 18) W20150608-21:47:40.722(1)? (STDERR) at new Polymerizer (packages/loneleeandr oo:polymerize/polymerize-server.coffee:186:23) W20150608-21:47:40.722(1)? (STDERR) at Package (packages/loneleeandroo:polym erize/polymerize-server.coffee:271:19) W20150608-21:47:40.722(1)? (STDERR) at packages/loneleeandroo:polymerize/pol ymerize-server.coffee:1:1 W20150608-21:47:40.722(1)? (STDERR) at packages/loneleeandroo:polymerize/pol ymerize-server.coffee:1:1 W20150608-21:47:40.722(1)? (STDERR) at E:\myProjs\github-repo\trunk\socioVD\ .meteor\local\build\programs\server\boot.js:222:10 W20150608-21:47:40.722(1)? (STDERR) at Array.forEach (native) W20150608-21:47:40.722(1)? (STDERR) at Function._.each._.forEach (C:\Users\r ohanray\AppData\Local\.meteor\packages\meteor-tool\1.1.3\mt-os.windows.x86_32\de v_bundle\server-lib\node_modules\underscore\underscore.js:79:11) W20150608-21:47:40.722(1)? (STDERR) at E:\myProjs\github-repo\trunk\socioVD\ .meteor\local\build\programs\server\boot.js:117:5 => Exited with code: 8 => Your application is crashing. Waiting for file change. Windows 8.1 64 bit. Meteor version # 1.1.0.2. Installed meteor packages:

meteor-platform autopublish insecure loneleeandroo:polymerize

Can you have a look?

[loneleeandroo]

Harlo :)

Thanks for trying out the package. Yep i'll have a look as soon as I get my hands on a windows environment in the next few hours ;)

Looking at the error, it seems to be pointing to this line of code:

path.relative(process.cwd(), process.env.PWD)

So I think I have a general idea of how to fix it.

[Akryum]

Any news on this issue?

[RodrigoLegendre]

Same problem here, but looking forward to trying this package ASA it's fixed!