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
Use case: if a user accidentally removes the APP_MIDDLEWARE export without expecting to, we should give them a heads up. We could do this by always logging the total app-attached middleware count on startup in dev mode, and additionally grepping the file for APP_MIDDLEWARE if the count is zero and logging a big message with steps to remedy the situation.
The text was updated successfully, but these errors were encountered:
I sort of want the boltzmann:routes run target to grow a bit and export middleware info, though maybe at that point it's not very routes-y and would need another name.
I sort of want the boltzmann:routes run target to grow a bit and export middleware info, though maybe at that point it's not very routes-y and would need another name.
This is valuable, & might be worth tracking as a separate issue!
Use case: if a user accidentally removes the
APP_MIDDLEWARE
export without expecting to, we should give them a heads up. We could do this by always logging the total app-attached middleware count on startup in dev mode, and additionally grepping the file forAPP_MIDDLEWARE
if the count is zero and logging a big message with steps to remedy the situation.The text was updated successfully, but these errors were encountered: