-
Notifications
You must be signed in to change notification settings - Fork 242
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
🐛 tech-insights-backend: Forbidden dependency on @backstage/backend-test-utils #1715
Comments
Are you seeing this error when importing |
when we are trying to run application via yarn dev then I am getting this jest not define. The thing is we are not able to find mockservice.ts inside backend/node_modules. when we tried to upgrade backstage version from 1.26 to 1.31 then we are getting this error. |
And this is getting from plugin tech-insigths. |
I see that the tech-insights backend has a production dependency on backend-test-utils: community-plugins/workspaces/tech-insights/plugins/tech-insights-backend/package.json Line 53 in fdb08e6
There's also no |
Contributions to fix this welcome 👍 |
🔖 Need
Issue: ReferenceError: jest is not defined
Context: We recently upgraded our Backstage version and created a custom TechInsights plugin. This plugin has a dependency on @backstage/backend-test-utils. When attempting to run yarn dev, we encounter the following error:
Steps Taken:
Error Details:
Request for Help: Could anyone provide guidance on how to resolve this ReferenceError? Specifically, how can we ensure that jest is properly defined and available in the context of mockServices.ts?
🎉 Proposal
Issue: ReferenceError: jest is not defined
Context: We recently upgraded our Backstage version and created a custom TechInsights plugin. This plugin has a dependency on @backstage/backend-test-utils. When attempting to run yarn dev, we encounter the following error:
when we checked this repo link for latest @backstage/backend-test-utils but after doing yarn install and yarn dev we are getting jest not define.
〽️ Alternatives
No response
❌ Risks
No response
👀 Have you spent some time to check if this RFC has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: