edison comments

Results 401 comments of


                                            edison

fix(custom-element): properly handle custom element remove then insert again

While fixing #12453, I realized I made a mistake and my previous review was incorrect. Your initial submission might have been correct. `this._resolved = false` will lead to the following...

Allow `~/path` as `<img src="~/...">` with `~` alias

This would be a breaking change. Currently ```html ``` is compiled to ```js import _imports_0 from 'fixtures/logo.png' ```

Allow `~/path` as `<img src="~/...">` with `~` alias

I agree with making this behavior configurable and made a PR #13462. Any suggestions are welcome.

enhance the warning when use undeclared variable in template

> No idea how to add test, because it will broken other test Could you please try to add an e2e test case?

feat: migrate linting to oxlint

@camc314 Thanks for this PR, but I think you should create the branch based on the minor branch instead of main.

feat: migrate linting to oxlint

Those deployments failed just related to `[email protected]`, pin `[email protected]` will resolve.

feat: migrate linting to oxlint

@camc314 uh, sorry, should be [email protected].

fix(types): support inferring inject in mixins

Could you please resolve the conflicts?

fix(custom-element): fix that boolean prop with default true can't updated to falsy value

/ecosystem-ci run

fix(custom-element): fix that boolean prop with default true can't updated to falsy value

/ecosystem-ci run nuxt