Skip to content

Conversation

@cigamit
Copy link
Contributor

@cigamit cigamit commented Jan 3, 2026

In dev, it is occasionally fail on new dev installs when starting npm, saying that it couldn't access the patternfly assets. They are clearly installed, so adding an alias to point to them as a stop gap.

@cigamit cigamit requested review from TheWitness and Copilot January 3, 2026 03:09
@cigamit cigamit self-assigned this Jan 3, 2026
@cigamit cigamit added bug Something isn't working build labels Jan 3, 2026
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR addresses intermittent issues with accessing PatternFly assets during development by adding webpack configuration to properly resolve asset paths.

Key Changes

  • Added PatternFly assets path to resolve-url-loader root configuration to support CSS url() resolution
  • Refactored webpack alias configuration to dynamically compute aliases for PatternFly assets
  • Added try-catch wrapper around alias computation to handle potential resolution failures

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working build

Development

Successfully merging this pull request may close these issues.

2 participants