Creating a side-effect free `new Component`

Is your feature request related to a problem? Please describe. When using a component in a JavaScript file, you do it like this:

import Component from `MyComponent.svelte`;

const myComponent = new Component({
   target: document.getElementById('main')
});

In our project we have the eslint rules no-new and no-unused-vars which get triggered by this code: The code triggers no-unused-vars, but if I remove const myComponent = , the code triggers the no-new rule.

Describe the solution you’d like I’d like the component to be able to do a “delayed mount”, to have a side-effect-free constructor if it does not receive a target property (for ease of use you can leave the default behavior like it is). Taking a peek at Vue, I’d like a syntax like this:

const myComponent = new Component();
myComponent.mount(document.getElementById('main'));

Describe alternatives you’ve considered For now, I’ll add a

// eslint-disable-next-line no-new
new Component({
   target: document.getElementById('main')
});

[ghost]

Assuming this issue is motivated by a desire to appease the linter without disabling the line, and you don’t actually need a separate mount function, an alterntive for you could be like this, for example:

(() => new App({
  target: document.getElementById('app'),
  hydrate: true,
  props: {}
}))()

[sw-yx]

not sure i understand. your motivations seem entirely because of no-new. yet your proposed syntax still includes new. why do you really want a delayed mount? your solution doesnt fit your stated problem.