Skip to content

[Package Error] "@material-ui/core@v5.0.0-alpha.24" could not be built.  #118

@oliviertassinari

Description

@oliviertassinari

https://cdn.skypack.dev/error/build:@material-ui/core@v5.0.0-alpha.24-v8z1nGS6umuoWBolkdHw

/*
 * [Package Error] "@material-ui/core@v5.0.0-alpha.24" could not be built. 
 *
 *   Installing package...
 *   Package "@material-ui/core/ExpansionPanel" not found. Have you installed it? 
 *   Package "@material-ui/core/ExpansionPanel" not found. Have you installed it?
 *
 * How to fix:
 *   - If you believe this to be an error in Skypack, file an issue here: https://github.com/pikapkg/cdn/issues
 *   - If you believe this to be an issue in the package, share this URL with the package authors to help them debug & fix.
 *   - Use https://pika.dev/ to find a web-friendly alternative to find another package.
 */

console.warn("[Package Error] \"@material-ui/core@v5.0.0-alpha.24\" could not be built. \nInstalling package...\nPackage \"@material-ui/core/ExpansionPanel\" not found. Have you installed it? \nPackage \"@material-ui/core/ExpansionPanel\" not found. Have you installed it?");
throw new Error("[Package Error] \"@material-ui/core@v5.0.0-alpha.24\" could not be built. ");
export default null;

The ExpansionPanel module doesn't exist anymore (only in v4), it's weird that it's surfacing here. I suspect that Skypack as a caching isolating issue between versions.

Context

I was trying to update our CDN demo that currently uses unpkg with this POC: https://codepen.io/oliviertassinari/pen/gOLOLKM

Notes

Use https://pika.dev/ to find a web-friendly alternative to find another package.

This sentence is semantically wrong.

https://github.com/pikapkg/cdn/issues

This link returns a 301.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions