Skip to content

Fix Web Awesome runtime error#451

Closed
SharonStrats wants to merge 1 commit into
stagingfrom
fix/web-awesome-error
Closed

Fix Web Awesome runtime error#451
SharonStrats wants to merge 1 commit into
stagingfrom
fix/web-awesome-error

Conversation

@SharonStrats

Copy link
Copy Markdown
Contributor

No description provided.

@SharonStrats SharonStrats self-assigned this Jul 21, 2026
Copilot AI review requested due to automatic review settings July 21, 2026 22:50
@SharonStrats SharonStrats moved this to In review in SolidOS NLNet UI Jul 21, 2026
@SharonStrats
SharonStrats changed the base branch from main to staging July 21, 2026 22:50

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

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 updates the Webpack module resolution configuration to prevent a runtime resolution error related to the @awesome.me/webawesome package by explicitly aliasing it to the installed node_modules location.

Changes:

  • Added a Webpack resolve.alias entry for @awesome.me/webawesome pointing at ./node_modules/@awesome.me/webawesome.

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

@SharonStrats

Copy link
Copy Markdown
Contributor Author

I don't think we need this now.

@github-project-automation github-project-automation Bot moved this from In review to Done in SolidOS NLNet UI Jul 26, 2026
@SharonStrats
SharonStrats deleted the fix/web-awesome-error branch July 26, 2026 02:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants