-
Notifications
You must be signed in to change notification settings - Fork 919
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle peerDependencies #55
Comments
For now, @pika/web leaves the actual package installing to npm, and just focuses on web-ifying your deps. Re-reading that error message though, and I feel like it could be more friendly. What about: "Make sure that the package was installed correctly and that the file exists." |
Fixed to a more friendly error message. |
drwpow
pushed a commit
that referenced
this issue
Jul 24, 2020
* make @snowpack/plugin-babel compatible with v2 * allow for sourcemaps
drwpow
pushed a commit
that referenced
this issue
Jul 27, 2020
* make @snowpack/plugin-babel compatible with v2 * allow for sourcemaps
drwpow
pushed a commit
that referenced
this issue
Jul 27, 2020
* make @snowpack/plugin-babel compatible with v2 * allow for sourcemaps
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Consider the case of
@apollo-elements/lit-apollo
:@apollo-elements/lit-apollo
relies on@apollo-elements/lib
which in turn relies ongraphql-tag
which has a peerDependency tographql
pikawebification produces:
Perhaps pika/web should install those peerDeps?
The text was updated successfully, but these errors were encountered: