Excluding tests from npm package distribution #72
Labels
Comments
aviaviavi
added
bug
|
Thanks for reporting @char0n, we will get this fixed ASAP |
This was referenced Nov 5, 2024
Merged
|
@aviaviavi any ETA on new 1.4.0 release? |
|
@char0n it's live as a |
|
@aviaviavi thanks, utilizing 1.4.0 version, will ping if any additional issues. |
char0n
added a commit
to swagger-api/swagger-js
that referenced
this issue
Nov 7, 2024
char0n
added a commit
to swagger-api/swagger-js
that referenced
this issue
Nov 7, 2024
|
I can confirm that the issue is resolved in v1.4.0 - swagger-api/swagger-ui#10197 (comment) |
|
Thanks for the update! We’ll go ahead and tag that release accordingly m.
…On Fri, Nov 8, 2024 at 1:57 AM Vladimír Gorej ***@***.***> wrote:
I can confirm that the issue is resolved in v1.4.0 - swagger-api/swagger-ui#10197
(comment)
<swagger-api/swagger-ui#10197 (comment)>
—
Reply to this email directly, view it on GitHub
<#72 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKS4JYIS5CENCMYKGIYFGLZ7SDHDAVCNFSM6AAAAABRHOCGJ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRUGI3TSOBSGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
npm package of scarf-js does include
test/*directory which is intended for development purposes only. It seems to causing issues with yarn + vitest combo.This was originally reported in swagger-api/swagger-ui#10197. I assume that because of #3, scarf is already disabled, but vitest from whatever reason tries to read tests from the installed scarf.js package.
The text was updated successfully, but these errors were encountered: