fix(deps): update dependency can-component to v4 - autoclosed

[renovate]

This PR contains the following updates:

Package	Type	Update	Change	References
can-component	dependencies	major	3.3.10 -> 4.4.11	homepage, source

---

Release Notes

canjs/can-component

v4.4.11

Compare Source

v4.4.10

Compare Source

Commit: 589b990. This test was assuming async teardown. Fixes in nodeLists and stache make this sync.

v4.4.9

Compare Source

#​315

v4.4.8

Compare Source

#​314

v4.4.7

Compare Source

#​312

v4.4.6

Compare Source

#​311

v4.4.5

Compare Source

Fix tests for IE11 #​308

v4.4.4

Compare Source

v4.4.3

Compare Source

PR: #​304

v4.4.2

Compare Source

v4.4.1

Compare Source

Properties in ViewModel can be initialized to null when instantiating a component

v4.4.0

Compare Source

Fixes #​292

count:from="count" works below:

can.Component.extend({
    tag: "my-counter",
    view: `
        <can-slot name="incrementButton"
            add:from="add">
            <button on:click="add(1)">+1</button>
        </can-slot>
        <can-slot name="countDisplay"
            count:from="count">
            {{count}}
        </can-slot>
    `,
    ViewModel: {
        count: {type: "number", default: 0},
        add(increment){
					debugger;
            this.count += increment;
        }
    }
});

v4.3.0

Compare Source

Adds a .viewModel property to component elements. can-view-model can take a hike!

v4.2.4

Compare Source

Fixed adding a programmatically-instantiated component that has already been torn down 2152734

v4.2.3

Compare Source

Fix an issue with programmatically-instantiated components not being torn down correctly #​277

v4.2.2

Compare Source

v4.2.1

Compare Source

v4.2.0

Compare Source

This release makes it possible to create new component instances with new, without rendering the instances in a template. This is useful when you:

• have complex logic for switching between different components (e.g. routing)
• want to create components without adding them to the page (e.g. testing)

The following defines a MyGreeting component and creates a my-greeting element by calling new on the component’s constructor function:

const HelloWorld = Component.extend({
	tag: "hello-world",
	view: `
		<can-slot name="greetingTemplate" />
		<content>world</content>
		<ul>{{#each(items)}} {{this}} {{/each}}</ul>
	`,
	ViewModel: {
		items: {}
	}
});

// Create a new instance of our component
const componentInstance = new HelloWorld({

	// values with which to initialize the component’s view model
	viewModel: {
		items: ["eat"]
	},

	// can-stache template to replace any <content> elements in the component’s view
	content: "<em>{{message}}</em>",

	// <can-template> strings rendered by can-stache with the scope
	templates: {
		greetingTemplate: "{{greeting}}"
	},

	// scope with which to render the <content> and templates
	scope: {
		greeting: "Hello",
		message: "friend"
	}
});

myGreetingInstance.element; // is like <my-greeting>Hello <em>friend</em> <ul> <li>eat</li> </ul></my-greeting>

myGreetingInstance.viewModel; // is HelloWorld.ViewModel{items: ["eat"]}

Changing the component’s view model will cause its element and any bindings to be updated:

myGreetingInstance.viewModel.items.push("sleep");

myGreetingInstance.element; // is like <my-greeting>Hello <em>friend</em> <ul> <li>eat</li> <li>sleep</li> </ul></my-greeting>

See the Programmatically instantiating a component section for details.

This release contains the following pull requests:

• Allow components to be instantiated with new #​237
• Add support for rendering components in stache templates #​238
• Allow components to be instantiated with <content /> #​240
• Allow components to be instantiated with viewModel bindings #​243
• Allow components to be instantiated with slot templates #​267
• Add "use strict" #​269

v4.1.3

Compare Source

v4.1.2

Compare Source

v4.1.1

Compare Source

Fix can-string dependency to <2.0.0 #​255

v4.1.0

Compare Source

v4.0.8

Compare Source

#​242

v4.0.7

Compare Source

#​231

v4.0.6

Compare Source

Filenames are now passed to stache() when using inline views like:

var MyComponent = Component.extend({
  tag: "my-filename-component",
  ViewModel: {},
  view: "<div></p>"
});

This way, useful error messages are given. For example, the view above gives:

MyFilenameComponentView:1: unexpected closing tag </p> expected </div>

#​229

v4.0.5

Compare Source

#​226

v4.0.4

Compare Source

v4.0.2

Compare Source

v4.0.1

Compare Source

can-dom-data-state was incorrectly listed in the devDependencies object.

v4.0.0

Compare Source

---

Renovate configuration

📅 Schedule: "on friday" in timezone America/Los_Angeles.

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "rebase!".

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot. View repository job log here.