Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Quiet the logs of universal-hot-reload #4

Closed
cereallarceny opened this issue Aug 24, 2020 · 1 comment
Closed

Quiet the logs of universal-hot-reload #4

cereallarceny opened this issue Aug 24, 2020 · 1 comment
Assignees
@cereallarceny
Labels
Priority: 2 - High 😰 Should be fixed as quickly as possible, ideally within the current or following sprint Severity: 3 - Medium 😒 Does not cause a failure, impair usability, or interfere with the system Status: Available 👋 Available for assignment, who wants it? Type: Improvement 📈 Performance improvement not introducing a new feature or requiring a major refactor
Milestone
1.0.0

Comments

@cereallarceny
Copy link
Owner

No need to fork, the library author has made it clear they intend on maintaining this repo. Create some PR's to allow for greater configuration of universal-hot-reload
@cereallarceny cereallarceny added Priority: 2 - High 😰 Should be fixed as quickly as possible, ideally within the current or following sprint Severity: 3 - Medium 😒 Does not cause a failure, impair usability, or interfere with the system Status: Available 👋 Available for assignment, who wants it? Type: Improvement 📈 Performance improvement not introducing a new feature or requiring a major refactor labels Aug 24, 2020
@cereallarceny cereallarceny added this to the 1.0.0 milestone Aug 24, 2020
@cereallarceny cereallarceny self-assigned this Aug 24, 2020
@cereallarceny
Copy link
Owner Author

Closed by yusinto/universal-hot-reload#31 and yusinto/universal-hot-reload#32

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

@cereallarceny cereallarceny

Labels
Priority: 2 - High 😰 Should be fixed as quickly as possible, ideally within the current or following sprint Severity: 3 - Medium 😒 Does not cause a failure, impair usability, or interfere with the system Status: Available 👋 Available for assignment, who wants it? Type: Improvement 📈 Performance improvement not introducing a new feature or requiring a major refactor
Projects
None yet
Milestone
1.0.0
Development

No branches or pull requests
1 participant
@cereallarceny