You are currently viewing the new Beta Editor Docs.
Switch to the Classic Editor Docs
You are currently viewing the Classic Editor Docs.
Switch to the Beta Editor Docs

Accessing Javascript

Interaction with Javascript objects in Anvil is primarily done through the anvil.js module. This reference provides some details about working with Javascript objects from Python code.

Check out the Quickstart guide for an introduction applied to an external library.

HTML Forms also have a unique way to interact with their HTML Template Javascript functions described here.

Accessing the window

You can access any Javascript function or variable by importing it from the window object. The window object can be thought of as the Javascript global namespace in the browser where your app runs.

from anvil.js.window import Foo
# Foo is a Javascript object defined in the Javascript namespace

Accessing a DOM Node

You can access the DOM node for any Anvil Component in Python

# access any anvil component's DOM node

Accessing an External Library

If you’ve found a Javascript library that you want to use within Anvil, always check the documentation and look for a browser option. Not all Javascript runs in the browser, and often library authors will provide a Javascript option specifically for the browser.

When a Javascript library has a browser version the code will look something like this:

<script src=""></script>

In the above example, a CDN provider hosts the Javascript library’s source code. By adding the script tags to our Native Libraries the Javascript source code will add objects as attributes to the window. We can then import the objects into Python using anvil.js.window. For an example of this approach, see how we load the Quill library in the Quickstart guide.

Almost all Javascript libraries are available at npmjs. Often you’ll find browser versions of those libraries hosted by CDN providers such as jsdelivr, unpkg or cdnjs. Be aware that finding a Javascript library on jsdelivr, unpkg or cdnjs does not guarantee its suitability for the browser.

You can avoid using a CDN provider by pasting the Javascript source code into a Javascript file in your assets. Then replacing the CDN provided URL with a relative URL.

<script src="_/theme/quill.js"></script>

A script tag with a src attribute is the traditional way to access Javascript files in the browser.

Javascript Modules

A more modern approach for working with Javascript in the browser is to use a Javascript module. The main difference is that a Javascript module does not add objects to the window. Instead, you explicitly import objects from the module. The library’s sample code will look something like this:

<script type="module">
  import { v4 as uuid4 } from '';


With Javascript modules we don’t need to paste the sample code into our Native Libraries. Instead, we can use anvil.js.import_from(URL) to access the Javascript objects directly in Python.

import anvil.js
uuid_module = anvil.js.import_from('')
uuid4 = uuid_module.v4
print(uuid4()) # 1b9d6bcd-bbfd-4b2d-9b5d-ab8dfbbd4bed

In the Javascript code above, v4 is a named import (aliased as uuid4). We access a named import in Python using . notation.

Javascript modules may also have a default import and you may see sample code like this:

<script type="module">
  import confetti from '';
  confetti(); // 🎉


Since confetti is not inside curly braces it is the default import (rather than a named import). In Python, the above sample code would become the following:

import anvil.js
confetti_module = anvil.js.import_from('')
confetti = confetti_module.default
confetti() # 🎉

anvil.js.import_from() always returns a Javascript Module object. You can then access the Javascript objects, as we’ve done above, with . notation.

Tip: is a CDN provider that only provides Javascript modules for the browser. If you can’t find a browser supported version of your preferred Javascript library you may find it at

Return values from anvil.js

When using anvil.js, Javascript objects will be returned as Python objects. Javascript strings, numbers, arrays, booleans, null, and undefined are mapped to their Python equivalents.

All other Javascript objects (including dictionary-like objects) will be returned as proxyobjects. Proxyobjects are Python objects that wrap a Javascript object and allow you to interact with the underlying Javascript object from Python code.

from anvil.js.window import Foo
print(type(Foo)) # <class 'Proxy'>

Return values from anvil.js.get_dom_node are also proxyobjects.

dom_node = anvil.js.get_dom_node(self.content_panel)
print(dom_node) # <HTMLDivElement proxyobject>

As is the window object!

print(anvil.js.window) # <Window proxyobject>

Catching Exceptions

When a Javascript Error is thrown within Javascript code, it is re-raised in Python as an ExternalError. You can catch Javascript errors in Python with anvil.js.ExternalError using a try/except block. If you need to access the original Javascript error, use the property .original_error.

import anvil.js
from anvil.js.window import Foo

except anvil.js.ExternalError as err:
    print(err) # this includes the string output of the original error
    js_error = err.original_error
    print(js_error.message) # most Javascript Errors have a message property
    print( # most Javsacript Errors have a name property

Working with proxyobjects


You can access the attributes on the underlying Javascript object in Python as you would in Javascript.     # use . notation
Foo['bar']  # use [] subscript notation

Javascript attributes will be returned to Python in the same way as described above i.e. Javascript strings, numbers, arrays, booleans, null, and undefined will be returned as their Python equivalents. All other Javascript objects will be returned as proxyobjects.

Calling dir() on a proxyobject, e.g. dir(Foo), will give an indication of the available attributes accessible in Python. Only Javascript enumerable properties of the underlying Javascript object will be returned when calling dir().

If you are using Javascript objects from an external library, it is always a good idea to check the documentation.

All proxyobjects have a keys() method e.g. Foo.keys(). Calling keys() returns a list of strings, which represents the underlying Javascript object’s own property names. It is the equivalent in Javascript of doing Object.keys(js_object)

All proxyobjects have a get() method e.g. Foo.get('bar', None). The default value will be returned if the attribute is not found. If no default value is provided then None will be used as the default value.


If an object is iterable in Javascript then it will be iterable in Python.
A Javascript object is only iterable if it has a Symbol.iterator symbol.

from anvil.js.window import jQuery

for element in jQuery('div'):
    # jQuery objects are iterable in Javascript
    # and therefore iterable in Python

Typically proxyobjects are not iterable - but you can iterate over the keys.

for key in proxy_obj.keys():
    val = proxy_obj[key]


Accessing .__class__ of a proxyobject will return the constructor of the underlying Javascript object.

x = Foo()
print(x)           # <Foo proxyobject>
print(x.__class__) # <proxyclass 'Foo'> (the Javascript constructor)
print(type(x))     # <class 'Proxy'>

True or False

All proxyobjects are considered ‘Truthy’ (i.e. bool(proxy_obj) will be True) unless:

  • the underlying Javascript object is empty: {}
  • the proxyobject can be called with len and len(proxy_obj) == 0


You can call len() on a proxyobject if the underlying Javascript object is not a function and has a .length property.

from anvil.js.window import jQuery

# jQuery objects have .length property and can be called with len()

Converting to Python

A proxyobject, which is a dictionary-like, is easily converted into a Python dictionary.

print(proxy_obj) # proxyobject({'a': 1, 'b': 2})
dict(proxy_obj)  # {'a': 1, 'b': 2}
{**proxy_obj}    # {'a': 1, 'b': 2} 

The above code works for all proxyobjects regardless of the underlying Javascript object. However, only the keys returned from the .keys() method will be included in the dictionary object. Thus it is unlikely to be suitable for most proxyobjects.

You can determine if the proxyobject is dictionary-like by inspecting it with print().

print(proxy_obj) # proxyobject({'a': 1, 'b': 2}) (dictionary-like)
print(Foo())     # <Foo proxyobject>      (not dictionary-like)

More specifically, a proxyobject is considered dictionary-like when the underlying Javascript object is an object literal.

Proxyobjects that are dictionary-like can be sent to the server. When a dictionary-like proxyobject is sent to the server, it will arrive as a plain Python dict. Other proxyobjects would need to be mapped to another portable type before being sent to the server.

Calling proxyobjects

If the underlying Javascript object is callable, then the proxyobject is callable in Python.
Kwargs will not work when calling proxyobjects since kwargs are not supported in Javascript.

When calling a proxyobject:

  • the arguments will be converted to Javascript,
  • the underlying Javascript function will be called with those arguments
  • the return value will be converted to Python.

If you send a Python function to a proxyobject as a callable, the reverse is true. See the Quickstart guide for an example.

You can know if a proxyobject is callable by calling print() on the proxyobject or by using callable().

from anvil.js.window import Foo

#   <proxyclass 'Foo'>, or
#   <proxyfunction 'Foo'>, or
#   <bound proxymethod 'Foo' of <Window proxyobject>>
# True

Calling with new

Some libraries will include constructors that require the use of the new operator.

When calling a proxyobject, Python will infer whether new should be used based on the context and the underlying Javascript object being called.

If you need to control when the new operator is used, you can use or

from anvil.js.window import Foo
import anvil.js, 1, 'a')  # Foo will be called with the new keyword, 1, 'a') # Foo will be called without the new keyword'Foo')['Foo'])
Are three ways of calling a Javascript function from Python

Calling asynchronous Javascript APIs

Some Javascript libraries will use asyncronous Promises. If your Javascript library includes an api that returns a Promise then you can write this code as syncronouse Python.

Here is an example from Vega (a Javascript graphing library).

var spec = "";

vegaEmbed('#vis', spec).then(function(result) {
    var vega_object = result;

According to the documentation vegaEmbed returns a Promise, which means we can’t access the vega_object until the Promise has resolved. Here’s how you might convert the above code into syncronous Python code in Anvil.

from anvil.js.window import vegaEmbed
dom_node = anvil.js.get_dom_node(self.vega_component) # a component you've added to your design view

spec = ""

vega_object = vegaEmbed(dom_node, spec) # replace '#vis' with a dom node
# We can wrap this in a try except 
# or let anvil's error handler deal with it

When an asynchronous Javascript function returns a Promise, Python blocks the execution until the Promise resolves before continuing. If the Promise rejects an exception is raised. The same mechanism described here is also used for

If you obtain a Promise object by some other route (for example, as the attribute of an object, or by constructing it directly), you can block until it resolves by calling anvil.js.await_promise(js_promise). This will return the resolved value of the Promise, or raise an exception if it rejects.

Using Python functions as callbacks

You can use Python functions as callbacks, or event handlers, for Javascript libraries. If you pass a callable Python object, Anvil wraps it as a Javascript function.

Blocking functions

When a Python function is called from Javascript, the function returns (or throws an exception) synchronously, like any Javascript function – unless it blocks. If the function blocks, it will return a Promise that resolves (or rejects) when the Python function returns (or raises an exception).

NB: A Python function blocks if the execution must wait for a process to complete before continuing. If you use sleep() or then you have written blocking code.

If you’re using a Python function as a callback, check the documentation of your Javascript library for the expected return value. Often callbacks, like the one used in our Quickstart, will work as expected regardless of whether the Python function blocks or not.

Note the above behaviour is different when a Python function is called from Javascript using where the return value is always a Promise.

Capturing exceptions in callbacks

Sometimes, the Javascript library you are using will handle exceptions itself. This can make it frustrating to debug your code, as it prevents Anvil from displaying information about the exception in the Output panel or the App Logs.

You can avoid this problem by adding the @anvil.js.report_exceptions decorator to your Python callback. This decorator will catch any exceptions thrown by that function and handle them via Anvil’s standard error-reporting mechanisms. (The callback will then return or resolve undefined to Javascript.)