Description
I tried to update this boilerplate to the latest meteor release but get stuck with an error on meteor start in the linking stage:
/home/xxx/.meteor/packages/meteor-tool/.1.4.3_1.raltwe++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/lib/node_modules/fibers/future.js:280
throw(ex);
^SyntaxError: Unexpected end of input
at Object.parse (native)
at /tools/fs/optimistic.js:204:17
at wrap.makeCacheKey._len2 (/tools/fs/optimistic.js:22:15)
at Entry._reallyRecompute (/home/quest/.meteor/packages/meteor-tool/.1.4.3_1.raltwe++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/lib/node_modules/optimism/lib/entry.js:215:26)
[ ... ]
Because I can abandon SSR in my project I already switched from flow-router-ssr to flow-router.
That didn't change anything on this error.
In meantime until there is a new flow-router maintainer or we get another ssr routing solution from MDG or the community, could you create a branch updated to the latest meteor release working without SSR?
That would help me a lot.
I already worked with react and komposer on several projects, but I am not really familliar with redux and webpack.
Unfortunatly I need subresource integrity in a current project which I plan to solve using a webpack plugin. To do that I of course need a running meteor/webpack project first :-/
(Will of course release my webpack-sri package if it works ;) )