jpwallace22 / react-lazify

VS Code Extension to create lazy imports in React

react-lazify's Issues

The automated release is failing 🚨

🚨 The automated release from the main branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

Cannot push to the Git repository.

semantic-release cannot push the version tag to the branch main on the remote Git repository with URL https://[secure]@github.com/jpwallace22/react-lazify.

This can be caused by:

• a misconfiguration of the repositoryUrl option
• the repository being unavailable
• or missing push permission for the user configured via the Git credentials on your CI environment

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

Implement `semantic-release`

Is your feature request related to a problem? Please describe.
The release process is tedious and has too much room for human error

Describe the solution you'd like
Implement semantic-release to automate the process

Describe alternatives you've considered
There are other software to implement other than semantic release, maybe do some research and ensure its the best use case.

Import looks for any 'react*' import

Describe the bug
If you don't have a react import (or maybe if you do... not 100% tested) it will latch onto another import that has react in its name. In this case react-hook-form

Screenshots

VS Code information

• OS: OSX 12.2.1
• Version 1.74.3

Dynamic imports as named

Describe the bug
When using the NextJS setting, dynamic is not being imported as a named imported

Expected behavior
Dynamic imports should be named from 'next/dynamic'