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.

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

docs(known-issues): log common problems and solutions #135

Closed
MFarabi619 opened this issue Oct 7, 2024 · 2 comments
Closed

docs(known-issues): log common problems and solutions #135

MFarabi619 opened this issue Oct 7, 2024 · 2 comments
Assignees

Comments

@MFarabi619
Copy link
Member

🆘 What is the problem at hand?

I often find myself running into the same problems and stumbling upon the same solutions. Not documenting these solutions costs valuable time in the future.

🚀 What is the impact of the problem? How is this problem important? How does it affect users/developers?

There are a number of problems that pop up consistently and have a definite solution pattern. Document these patterns so that others can save both their time and sanity.

Start with the following:

  • Builds for apps fail in CI/CD if playwright isn't installed first. Not sure why, triage further.
  • Nx commands will fail after a lib/app is initialized, as it initializes them in .cjs by default. This can be fixed by modifying the ESlint config and the TS config.
@github-project-automation github-project-automation bot moved this to ⏭ Todo in 🐞 2025 Oct 7, 2024
@HasithDeAlwis HasithDeAlwis removed their assignment Oct 16, 2024
@HasithDeAlwis HasithDeAlwis moved this from ⏭ Todo to 💀 Backlog in 🐞 2025 Oct 16, 2024
@HasithDeAlwis HasithDeAlwis self-assigned this Oct 16, 2024
@HasithDeAlwis HasithDeAlwis moved this from 💀 Backlog to ⏭ Todo in 🐞 2025 Oct 16, 2024
@JeremyFriesenGitHub
Copy link
Contributor

hello, would migration fix this issue? i've logged a new bug #193, should that have been written in here or should we make just full issues about this?

@MFarabi619
Copy link
Member Author

hello, would migration fix this issue? i've logged a new bug #193, should that have been written in here or should we make just full issues about this?

@JeremyFriesenGitHub Let's talk about it after the meeting this evening

@HasithDeAlwis HasithDeAlwis moved this from ⏭ Todo to ✅ Done in 🐞 2025 Dec 4, 2024
@HasithDeAlwis HasithDeAlwis closed this as completed by moving to ✅ Done in 🐞 2025 Dec 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: ✅ Done
Development

No branches or pull requests

3 participants