You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that the system is trying to access a src/builder.ts file, which does not exist in the installed version of @sanity/image-url. This issue is happening during a CI/CD pipeline using Azure Pipelines, but I also confirmed that this file doesn't exist locally in node_modules.
To Reproduce
Steps to reproduce the behavior:
Set up a project using @sanity/image-url in a Next.js application.
Deploy the application in an Azure Pipelines environment.
During the build process, the error is triggered when trying to access the missing src/builder.ts file.
Expected behavior
The build should reference the compiled files from the lib/ folder, not the source files from src/, and the process should complete without errors.
Screenshots
@sanity/image-url: ^1.0.2 Local: Windows 10 CI/CD: Azure Pipelines (Linux-based agent)
npm: 9.8.1 node: v18.17.1
The text was updated successfully, but these errors were encountered:
It seems that the system is trying to access a src/builder.ts file, which does not exist in the installed version of @sanity/image-url. This issue is happening during a CI/CD pipeline using Azure Pipelines, but I also confirmed that this file doesn't exist locally in node_modules.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The build should reference the compiled files from the lib/ folder, not the source files from src/, and the process should complete without errors.
Screenshots
@sanity/image-url: ^1.0.2
Local: Windows 10
CI/CD: Azure Pipelines (Linux-based agent)
npm: 9.8.1
node: v18.17.1
The text was updated successfully, but these errors were encountered: