Replies: 2 comments
-
|
Hi 👋 Great to hear that you’ve already set up the project locally and successfully ran A good next step is to look for issues labeled "good first issue" or "documentation" in the webpack repositories. These are usually beginner-friendly and focus on small fixes such as improving documentation, correcting typos, or updating examples. You can search for them here: https://github.com/search?q=org%3Awebpack+label%3A%22good+first+issue%22&type=issues If you're interested in documentation improvements, the documentation repository is also a great place to start: https://github.com/webpack/webpack.js.org Before working on an issue, it’s also helpful to read the contributing guide: https://github.com/webpack/webpack/blob/main/CONTRIBUTING.md Since you already have the project running locally, you’re in a great position to start picking up small tasks and submitting your first pull request. Good luck with your contributions! |
Beta Was this translation helpful? Give feedback.
-
|
Hey @mahi1910, Dependency resolution and plugin configuration in Webpack can get messy quickly. Checking if a recent loader version update (or Babel mismatch) caused a breaking change might be the fastest way to isolate the issue. Let us know if you find the root configuration bug! Let me know if you make any progress or if you need another fresh set of eyes on it! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I would like to work on good first issue . I have set up project locally done successfully yarn test and would appreciate any guidance
Beta Was this translation helpful? Give feedback.
All reactions