> For the complete documentation index, see [llms.txt](https://cbwire.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cbwire.ortusbooks.com/cbwire-v1/essentials/events.md).

# Events

You can fire events from within views, components, or by using the global `cbwire` JavaScript object.

### From View

```markup
<button wire:click="$emit( 'counterIncremented' )">
```

### From Component

```javascript
this.emit( "counterIncremented" );
```

### From Javascript Global

```xml
<script>
    cbwire.emit( 'counterIncremented' );
</script>
```

## Event Listeners

You can register event listeners on a component by defining `variables.listeners`.

```javascript
component extends="cbwire.models.Component"{

	variables.listeners = {
		"counterIncremented": "tweetAboutIt"
	};

	function tweetAboutIt(){
		// Blow up Twitter
	}

	...
}
```

{% hint style="success" %}
cbwire will invoke the `tweetAboutIt` method on the component if any other component on the same page emits a `counterIncremented` event.&#x20;
{% endhint %}

{% hint style="info" %}
When defining your listeners, it is good to put your listener's names in quotation marks, as we have in our component above. \
\
`"counterIncremented": "tweetAboutIt"`

JavaScript keys are case-sensitive. You can preserve the key casing in CFML by surrounding your listener names in quotations. Without the quotations, CFML will convert the key to all uppercase, such as `TWEETABOUTIT`. :upside\_down:&#x20;
{% endhint %}

## Event Listeners In JavaScript

```javascript
// File: ./views/wires/myView.cfm
<script>
    cbwire.on( 'counterIncremented', counter => {
        alert( 'The counter was incremented with a value of: ' + counter );
    })
</script>
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cbwire.ortusbooks.com/cbwire-v1/essentials/events.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.