Adam Hines
Adam Hines
@babel/core recently made a change where the sourcemap is no longer a plain js object, but instead is a class SourceMap. This breaks when the coverage data gets passed into...
A change introduced in v28.1.0 in PR #471 unintentionally changed the behavior of the tsconfig parsing such that configs using "extends" were no longer being considered. Fixes: #495
The code currently generated by this plugin looks something like the following when building a library: src/index.js ```js export {default as Foo} from './component.vue'; ``` ```js var __component__ = /*#__PURE__*/...
When yarn installing this package, I receive the following error: ``` ➤ YN0000: ┌ Resolution step ➤ YN0002: │ @pinia/testing@npm:0.0.14 [329d6] doesn't provide vue (pa561a), requested by vue-demi ➤ YN0000:...
### Describe the bug When rollup produce errors during build, the error message that is displayed does not always contain the relevant information such as which file produced the error,...
### Description The code which modified the error message to have additional context about the module id and code frame where the error originated was relying on the error's stack...
`@vue/server-renderer` and `@vue/compiler-dom` were both required in the sense that they will throw regardless of whether or not your are using functionality from those libraries if they weren't installed. I...
My team has been discussing using this library, but there has been some debate on what the intended pronunciation is. Is it Ky (pronounced `/kiː/` like “Key”), or Ky (pronounced...
Fixes #7070 ### Description Vite 6 no longer applies default conditions when you override resolve.conditions. This PR adds them back conditionally based on the vite version. ### Please don't delete...
### Describe the bug When using a browser-based evironment (happy-dom, jsdom, ~browser~), vitest still passes `conditions: ['node']` in the resolve config. When using Vite 5, this doesn't really matter because...