You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A workaround is to set the following in your mimosa-config.coffee (or the equivalent in your mimosa-config.js):
webPackage:
appjs: undefined
If you run into this problem, it's probably because you don't actually have a server to run, so adding the above to your config is something you should do anyway, but Mimosa shouldn't crash if you setup your config incorrectly.
I would just patch this and submit a PR, but I'm not sure what the value of serverRelPath should be if server is not defined. Just "." maybe?
The text was updated successfully, but these errors were encountered:
When mimosa-config.coffee (or .js) contains the web-package module, but
no server config section (or a server config section with no path:
entry), then the crash would occur.
Added code to config.coffee to set the config.webPackage.appjs to
undefined in this case so that the code generation step is bypassed.
Also handles the case where you have a server: section in your
mimosa-config.coffee file, but no path: entry.
The following line crashes when your mimosa-config file has no server entries:
See https://github.com/dbashford/mimosa-web-package/blob/master/src/index.coffee#L174
A workaround is to set the following in your mimosa-config.coffee (or the equivalent in your mimosa-config.js):
If you run into this problem, it's probably because you don't actually have a server to run, so adding the above to your config is something you should do anyway, but Mimosa shouldn't crash if you setup your config incorrectly.
I would just patch this and submit a PR, but I'm not sure what the value of serverRelPath should be if server is not defined. Just "." maybe?
The text was updated successfully, but these errors were encountered: