Skip to content

Fix webpack config#461

Draft
hypery2k wants to merge 4 commits intodevelopfrom
bugfix/webpack-config
Draft

Fix webpack config#461
hypery2k wants to merge 4 commits intodevelopfrom
bugfix/webpack-config

Conversation

@hypery2k
Copy link
Collaborator

📝 Description

🎯 Relevant issues

💎 Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

📜 Example code

🚦 How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

  • Test A
  • Test B

🏁 Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • I have commented my code, particularly in hard-to-understand areas

We used this to notify people about the funding of our project but this
is now handled by npm natively via fund in the package and via npm fund.
Furthermore the dependency is no longer maintained (last update is
6 years ago).
@hypery2k hypery2k force-pushed the bugfix/webpack-config branch from 2a60c57 to aa8a47b Compare October 12, 2023 15:31
@hypery2k hypery2k force-pushed the bugfix/webpack-config branch from aa8a47b to fb36632 Compare November 2, 2023 18:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant