Show friendly error if 'micro' peer dependency isn't met #96
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I got too excited to use
micro-dev
and installed it without regarding thenpm WARN
about my unmetmicro
peer dependency. The resultingCannot find module 'micro/lib'
error didn't spark an immediate understanding of the fix.This change validates the availability of
micro
, and provides a friendlier error if it's missing.I'd meant to use
micro-dev
to simulate Now V2's routing (starting from this comment)—since this was only in a development context I hadn't made a point of installingmicro
too. Although my error required a a few willful missteps on my part, my mistakes feel like the sort that other devs getting comfortable withmicro-dev
could make.