Closed MastroLindus closed 1 year ago
Nothing looks familiar… sorry
I'm getting the same error but I am not using this package. My packages are:
# Meteor packages used by this project, one per line.
# Check this file (and the other files in this directory) into your repository.
#
# 'meteor add' and 'meteor remove' will edit this file for you,
# but you can also edit it by hand.
meteor-base@1.4.0 # Packages every Meteor app needs to have
mobile-experience@1.1.0 # Packages for a great mobile UX
mongo@1.11.0 # The database Meteor supports right now
standard-minifier-css@1.7.2 # CSS minifier run for production mode
standard-minifier-js@2.6.0 # JS minifier run for production mode
es5-shim@4.8.0 # ECMAScript 5 compatibility for older browsers
ecmascript@0.15.1 # Enable ECMAScript2015+ syntax in app code
typescript@4.2.2 # Enable TypeScript syntax in .ts and .tsx modules
shell-server@0.5.0 # Server-side component of the `meteor shell` command
tracker@1.2.0 # Dependency tracker to allow reactive callbacks
static-html # Define static page content in .html files
akryum:vue-component # Vue-CLI template to publish components
meteortesting:mocha # A package for writing and running your meteor app and package tests with mocha
mdg:validated-method
alanning:roles
accounts-base@1.9.0
accounts-password@1.7.0
socialize:user-presence
lacosta:method-hooks
peerlibrary:middleware
check@1.3.1
meteorhacks:async
xolvio:cleaner
meteorhacks:ssr
montiapm:agent
tunguska:reactive-aggregate
Any idea to resolve it?
It was already solved but I don't know why xD. I restarted the Dyno (server) twice and it worked. Maybe it caused by free tier of Heroku and these issues can happen.
closing
I am aware that this plugin has nothing to do with deployments to Heroku, but for some reason using it makes our app crash with a heap out of memory.
Replacing the plugin with the official one fixes the problem, and that's weird as I could have expected an error during compilation, but I am surprised to see one at runtime. Do you have any clues on what could be causing this behavior?