▲ The built image size (417.0M) exceeds the 100MiB limit about meteor-now HOT 10 CLOSED

@jkrup Here's what I've tried:

Add the following code to packages.json (per zeit now docs):
"now": { "features": { "cloud": "v1" } }

Add "'features': { 'cloud': 'v1' }" to a secret on now, then include it as `@cloud-settings in meteor-now deployment string

Add "'features': { 'cloud': 'v1' }" to the end of the meteor now deployment string on its own. The meteor now codebase seems to accommodate remainingVariables but not sure how this fits in, or what use case remainingVariables would cover.

None of the above works, but I'll keep working on it until something breaks through as I need it to work yesterday for a customer.

I'm currently looking into how the now.features.cloud version could be integrated into the deployment string as an additional env variable.

I thought the above information might be helpful in identifying the first order issue. I'll let you know if I'm able to develop a solution that works on my own through pull-request.

from meteor-now.

@qualitymanifest I think it would need to be an option made available in the deployment string of meteor-now. Either that or baked into the deployment as the only option. So, it will require a change to meteor-now as far as I can tell.

Still working out the details, but will post an update with any progress.

from meteor-now.

Success! Deployment ready
Thank you @jkrup !

from meteor-now.

I have the same issue: The built image size (346.2M) exceeds the 100MiB limit

My app is 84 MB locally. Is the issue caused by meteor-now or is the app somehow growing 268 MB once it gets to Zeit's servers?

Here's more on the reason for the change on zeit: this issue vercel/vercel#1523

from meteor-now.

Does the bundle-splitting of 1MB for the free ZEIT plan need to be used to split files into 100MB chunks for the paid ZEIT plan? Is there some limit on ZEIT of 100MB per file upload?

from meteor-now.

Zeit made an improvement that requires under 100MB to deploy to cloud version 2, which they made standard for all deployments. Deploying to cloud: 'v1' still allows larger file sizes.

 "features": {
    "cloud": "v1"
  },

A quick solution to the current issue in meteor-now would be to change the setting.

I can try to do it by pull request, but it could take a while as I'm unfamiliar with the code.

from meteor-now.

@brianmcdonough have you had success deploying to cloud v1 using meteor-now? If so, how did you go about it? I was actually just writing #121 when you posted that. I've tried several ways and I can't get it to work.

from meteor-now.

I've attempted to reduce build sizes with node alpine, but especially for apps bundled with mongodb that may be very tricky (or not possible). So for now I'll quickly push an update as per @brianmcdonough 's comment to add a now.json with "'features': { 'cloud': 'v1' }"

from meteor-now.

Everyone having this issue please try npm install meteor-now@beta and then redeploying using meteor-now

from meteor-now.

#123

from meteor-now.