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
The reason will be displayed to describe this comment to others. Learn more.
somehow, npx on my Semaphore CI instance is failing, I'm suspecting 1.2.0 of this program — I get Error: Cannot find module '/home/semaphore/.npm/_npx/d5cad42883f80c/node_modules/lines-and-columns/build/index.mjs'.
Is it possible that somehow beaking 1.2.0 is automatically consumed because of a caret semver (like they have it here) — I tried to dig npx itself but can't find any references via GH searches on public npm org...
I wonder, would it make sense to publish 1.2.1 without esm and named exports? Or somehow to take down the 1.2.0?
The reason will be displayed to describe this comment to others. Learn more.
Update: I made another mistake and published 1.1.9 and 1.2.1 with ESM support. This broke any importers that were themselves ESM because they previously would have accessed LinesAndColumns.default. Versions 1.1.10 and 1.2.3 fix that issue and should be equivalent to 1.1.6.
b62d791
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
somehow, npx on my Semaphore CI instance is failing, I'm suspecting
1.2.0
of this program — I getError: Cannot find module '/home/semaphore/.npm/_npx/d5cad42883f80c/node_modules/lines-and-columns/build/index.mjs'
.Is it possible that somehow beaking 1.2.0 is automatically consumed because of a caret semver (like they have it here) — I tried to dig
npx
itself but can't find any references via GH searches on public npm org...I wonder, would it make sense to publish
1.2.1
without esm and named exports? Or somehow to take down the1.2.0
?b62d791
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like the Author is already looking into the issue, but for the sake of prosperity, we are also having a similar with our Vue linting service.
b62d791
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you were previously using 1.1.6 (which everyone was) then 1.1.9 should work for you. Sorry about that!
b62d791
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1.2.1 should also work fine (it's the same as 1.1.9).
b62d791
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Update: I made another mistake and published 1.1.9 and 1.2.1 with ESM support. This broke any importers that were themselves ESM because they previously would have accessed
LinesAndColumns.default
. Versions 1.1.10 and 1.2.3 fix that issue and should be equivalent to 1.1.6.b62d791
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thank you for a quick fix, I can confirm the CI is building, the fixed deps trickled through