caught (in promise) typeerror assignment to constant variable

TypeError: Assignment to Constant Variable in JavaScript

Last updated: Mar 2, 2024 Reading time · 3 min

# TypeError: Assignment to Constant Variable in JavaScript

The "Assignment to constant variable" error occurs when trying to reassign or redeclare a variable declared using the const keyword.

When a variable is declared using const , it cannot be reassigned or redeclared.

Here is an example of how the error occurs.

# Declare the variable using let instead of const

To solve the "TypeError: Assignment to constant variable" error, declare the variable using the let keyword instead of using const .

Variables declared using the let keyword can be reassigned.

We used the let keyword to declare the variable in the example.

Variables declared using let can be reassigned, as opposed to variables declared using const .

You can also use the var keyword in a similar way. However, using var in newer projects is discouraged.

# Pick a different name for the variable

Alternatively, you can declare a new variable using the const keyword and use a different name.

We declared a variable with a different name to resolve the issue.

The two variables no longer clash, so the "assignment to constant" variable error is no longer raised.

# Declaring a const variable with the same name in a different scope

You can also declare a const variable with the same name in a different scope, e.g. in a function or an if block.

The if statement and the function have different scopes, so we can declare a variable with the same name in all 3 scopes.

However, this prevents us from accessing the variable from the outer scope.

# The const keyword doesn't make objects immutable

Note that the const keyword prevents us from reassigning or redeclaring a variable, but it doesn't make objects or arrays immutable.

We declared an obj variable using the const keyword. The variable stores an object.

Notice that we are able to directly change the value of the name property even though the variable was declared using const .

The behavior is the same when working with arrays.

Even though we declared the arr variable using the const keyword, we are able to directly change the values of the array elements.

The const keyword prevents us from reassigning the variable, but it doesn't make objects and arrays immutable.

# Additional Resources

You can learn more about the related topics by checking out the following tutorials:

• SyntaxError: Unterminated string constant in JavaScript
• TypeError (intermediate value)(...) is not a function in JS

Borislav Hadzhiev

Web Developer

Copyright © 2024 Borislav Hadzhiev

Troubleshooting and Fixing TypeError – Assignment to Constant Variable Explained

Introduction.

TypeError is a common error in JavaScript that occurs when a value is not of the expected type. One specific type of TypeError that developers often encounter is the “Assignment to Constant Variable” error. In this blog post, we will explore what a TypeError is and dive deep into understanding the causes of the “Assignment to Constant Variable” TypeError.

Causes of TypeError: Assignment to Constant Variable

The “Assignment to Constant Variable” TypeError is triggered when a developer attempts to modify a value assigned to a constant variable. There are a few common reasons why this error might occur:

Declaring a constant variable using the const keyword

One of the main causes of the “Assignment to Constant Variable” TypeError is when a variable is declared using the const keyword. In JavaScript, the const keyword is used to declare a variable that cannot be reassigned a new value. If an attempt is made to assign a new value to a constant variable, a TypeError will be thrown.

Attempting to reassign a value to a constant variable

Another cause of the “Assignment to Constant Variable” TypeError is when a developer tries to reassign a new value to a variable declared with the const keyword. Since constant variables are by definition, well, constant, trying to change their value will result in a TypeError.

Scoping issues with constant variables

Scoping plays an important role in JavaScript, and it can also contribute to the “Assignment to Constant Variable” TypeError. If a constant variable is declared within a specific scope (e.g., inside a block), any attempts to modify its value outside of that scope will throw a TypeError.

Common Scenarios and Examples

Scenario 1: declaring a constant variable and reassigning a value.

In this scenario, let’s consider a situation where a constant variable is declared, and an attempt is made to reassign a new value to it:

Explanation of the error:

When the above code is executed, a TypeError will be thrown, indicating that the assignment to the constant variable myVariable is not allowed.

Code example:

Troubleshooting steps:

• Double-check the declaration of the variable to ensure that it is indeed declared using const . If it is declared with let or var , reassigning a value is allowed.
• If you need to reassign a value to the variable, consider declaring it with let instead of const .

Scenario 2: Modifying a constant variable within a block scope

In this scenario, let’s consider a situation where a constant variable is declared within a block scope, and an attempt is made to modify its value outside of that block:

The above code will produce a TypeError, indicating that myVariable cannot be reassigned outside of the block scope where it is declared.

• Ensure that you are referencing the constant variable within the correct scope. Trying to modify it outside of that scope will result in a TypeError.
• If you need to access the variable outside of the block, consider declaring it outside the block scope.

Best Practices for Avoiding TypeError: Assignment to Constant Variable

Understanding when to use const vs. let.

In order to avoid the “Assignment to Constant Variable” TypeError, it’s crucial to understand the difference between using const and let to declare variables. The const keyword should be used when you know that the value of the variable will not change. If you anticipate that the value may change, consider using let instead.

Properly scoping constant variables

It’s essential to also pay attention to scoping when working with constant variables. Make sure that you are declaring the variables in the appropriate scope and avoid trying to modify them outside of that scope. This will help prevent the occurrence of the “Assignment to Constant Variable” TypeError.

Considerations for handling immutability

Immutability is a concept that is closely related to constant variables. Sometimes, using const alone may not be enough to enforce immutability. In such cases, you may need to use techniques like object freezing or immutable data structures to ensure that values cannot be modified.

In conclusion, the “Assignment to Constant Variable” TypeError is thrown when there is an attempt to modify a value assigned to a constant variable. By understanding the causes of this error and following best practices such as using const and let appropriately, scoping variables correctly, and considering immutability, you can write code that avoids this TypeError. Remember to pay attention to the specific error messages provided, as they can guide you towards the source of the problem and help you troubleshoot effectively.

By keeping these best practices in mind and understanding how to handle constant variables correctly, you can write cleaner and more reliable JavaScript code.

Related posts:

• Mastering Assignment to Constant Variable – Understanding the Syntax and Best Practices
• JavaScript Variable Types – Exploring the Differences Between var, let, and const
• Understanding the Differences – const vs let vs var – Which One to Use?
• Understanding Constant Variables in Java – A Complete Guide
• Understanding Assignment to Constant Variable – Tips and Strategies for Effective Programming

关于“TypeError: Assignment to constant variable”的问题解决方案

在项目开发过程中，在使用变量声明时，如果不注意，可能会造成类型错误 比如：

Uncaught (in promise) TypeError: Assignment to constant variable. 未捕获的类型错误：赋值给常量变量。

我们使用 const 定义了变量且存在初始值。 后面又给这个变量赋值，所以报错了。

ES6 标准引入了新的关键字 const 来定义常量， const 与 let 都具有块级作用域：

• 使用 const 定义的常量，不能修改它的值，且定义的常量必须赋初值；
• let 定义的是变量，可以进行变量赋值操作，且不需要赋初值。

这个错误就是因为我们修改了常量而引起的错误，虽然某些浏览器不报错，但是无效果！

将 const 改为 let 进行声明。

请填写红包祝福语或标题

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。 2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

What's new

How to Fix Assignment to Constant Variable

Last updated on September 7, 2023 at 4:22 PM

Krste Rajchevski

Software Engineer @ Bugpilot

Annoyed by React errors? Bugpilot is the error monitoring platform for React. Catch unexpected errors, troubleshoot, and fix with our AI assistant. Learn more and create an account to start your 14-day free trial.

If you're a JavaScript developer, you might have come across the dreaded TypeError: Assignment to constant variable error at some point. This error occurs when you try to assign a new value to a variable that has been declared as a constant using the const keyword. In JavaScript, constants are variables whose values cannot be changed once they are assigned. This error is thrown as a result of violating this rule. In this blog post, we will explore the reasons behind this error, discuss common scenarios where it might occur, and provide two possible solutions to fix it.

Understanding the Error

When you declare a variable using the const keyword, you are explicitly stating that the variable's value cannot be modified. Therefore, if you attempt to assign a new value to a constant variable, JavaScript will raise a TypeError with the message "Assignment to constant variable."

Possible Scenarios

Let's consider a simple example to better understand when this error might occur. Imagine you are developing a JavaScript application to calculate the area of a circle. In your code, you declare a constant variable named pi to store the value of Pi. However, mistakenly, you later attempt to reassign a new value to pi , causing the TypeError to be thrown.

In the above example, we try to assign a new value to the pi variable, which was declared as a constant. This violates the principle of immutability that constants adhere to, leading to the error.

Solutions to the Error

Solution 1: use a mutable variable.

One possible solution to fix the Assignment to constant variable error is to use a mutable variable instead of a constant. By declaring the variable using the let or var keyword, you allow the value to be reassigned as needed.

Solution 2: Choose a New Variable Name

Another solution is to select a different variable name and declare it as a constant. This is useful when you need to update the value of a variable but want to adhere to the principle of immutability.

By changing the variable name, you avoid violating the immutability principle and resolve the error.

The TypeError: Assignment to constant variable error occurs when you try to reassign a new value to a variable that has been declared as a constant. Understanding the concept of constants in JavaScript and following the principles of immutability can help you avoid this error. In this blog post, we explored why this error happens, discussed a common scenario where it might occur, and provided two possible solutions to fix it. Remember to carefully consider the use of constants when writing your JavaScript code to prevent this error from occurring. Happy coding!

Was this article helpful?

• Skip to main content
• Select language
• Skip to search

TypeError: invalid assignment to const "x"

Const and immutability, what went wrong.

A constant is a value that cannot be altered by the program during normal execution. It cannot change through re-assignment, and it can't be redeclared. In JavaScript, constants are declared using the const keyword.

Invalid redeclaration

Assigning a value to the same constant name in the same block-scope will throw.

Fixing the error

There are multiple options to fix this error. Check what was intended to be achieved with the constant in question.

If you meant to declare another constant, pick another name and re-name. This constant name is already taken in this scope.

const , let or var ?

Do not use const if you weren't meaning to declare a constant. Maybe you meant to declare a block-scoped variable with let or global variable with var .

Check if you are in the correct scope. Should this constant appear in this scope or was is meant to appear in a function, for example?

The const declaration creates a read-only reference to a value. It does not  mean the value it holds is immutable, just that the variable identifier cannot be reassigned. For instance, in case the content is an object, this means the object itself can still be altered. This means that you can't mutate the value stored in a variable:

But you can mutate the properties in a variable:

Document Tags and Contributors

• JavaScript basics
• JavaScript first steps
• JavaScript building blocks
• Introducing JavaScript objects
• Introduction
• Grammar and types
• Control flow and error handling
• Loops and iteration
• Expressions and operators
• Numbers and dates
• Text formatting
• Regular expressions
• Indexed collections
• Keyed collections
• Working with objects
• Details of the object model
• Iterators and generators
• Meta programming
• A re-introduction to JavaScript
• JavaScript data structures
• Equality comparisons and sameness
• Inheritance and the prototype chain
• Strict mode
• JavaScript typed arrays
• Memory Management
• Concurrency model and Event Loop
• References:
• ArrayBuffer
• AsyncFunction
• Float32Array
• Float64Array
• GeneratorFunction
• InternalError
• Intl.Collator
• Intl.DateTimeFormat
• Intl.NumberFormat
• ParallelArray
• ReferenceError
• SIMD.Bool16x8
• SIMD.Bool32x4
• SIMD.Bool64x2
• SIMD.Bool8x16
• SIMD.Float32x4
• SIMD.Float64x2
• SIMD.Int16x8
• SIMD.Int32x4
• SIMD.Int8x16
• SIMD.Uint16x8
• SIMD.Uint32x4
• SIMD.Uint8x16
• SharedArrayBuffer
• StopIteration
• SyntaxError
• Uint16Array
• Uint32Array
• Uint8ClampedArray
• WebAssembly
• decodeURI()
• decodeURIComponent()
• encodeURI()
• encodeURIComponent()
• parseFloat()
• Arithmetic operators
• Array comprehensions
• Assignment operators
• Bitwise operators
• Comma operator
• Comparison operators
• Conditional (ternary) Operator
• Destructuring assignment
• Expression closures
• Generator comprehensions
• Grouping operator
• Legacy generator function expression
• Logical Operators
• Object initializer
• Operator precedence
• Property accessors
• Spread syntax
• async function expression
• class expression
• delete operator
• function expression
• function* expression
• in operator
• new operator
• void operator
• Legacy generator function
• async function
• for each...in
• try...catch
• Arguments object
• Arrow functions
• Default parameters
• Method definitions
• Rest parameters
• constructor
• element loaded from a different domain for which you violated the same-origin policy." href="Property_access_denied.html">Error: Permission denied to access property "x"
• InternalError: too much recursion
• RangeError: argument is not a valid code point
• RangeError: invalid array length
• RangeError: invalid date
• RangeError: precision is out of range
• RangeError: radix must be an integer
• RangeError: repeat count must be less than infinity
• RangeError: repeat count must be non-negative
• ReferenceError: "x" is not defined
• ReferenceError: assignment to undeclared variable "x"
• ReferenceError: deprecated caller or arguments usage
• ReferenceError: invalid assignment left-hand side
• ReferenceError: reference to undefined property "x"
• SyntaxError: "0"-prefixed octal literals and octal escape seq. are deprecated
• SyntaxError: "use strict" not allowed in function with non-simple parameters
• SyntaxError: "x" is a reserved identifier
• SyntaxError: JSON.parse: bad parsing
• SyntaxError: Malformed formal parameter
• SyntaxError: Unexpected token
• SyntaxError: Using //@ to indicate sourceURL pragmas is deprecated. Use //# instead
• SyntaxError: a declaration in the head of a for-of loop can't have an initializer
• SyntaxError: applying the 'delete' operator to an unqualified name is deprecated
• SyntaxError: for-in loop head declarations may not have initializers
• SyntaxError: function statement requires a name
• SyntaxError: invalid regular expression flag "x"
• SyntaxError: missing ) after argument list
• SyntaxError: missing ; before statement
• SyntaxError: missing = in const declaration
• SyntaxError: missing ] after element list
• SyntaxError: missing formal parameter
• SyntaxError: missing variable name
• SyntaxError: missing } after property list
• SyntaxError: redeclaration of formal parameter "x"
• SyntaxError: return not in function
• SyntaxError: test for equality (==) mistyped as assignment (=)?
• SyntaxError: unterminated string literal
• TypeError: "x" has no properties
• TypeError: "x" is (not) "y"
• TypeError: "x" is not a constructor
• TypeError: "x" is not a function
• TypeError: "x" is read-only
• TypeError: More arguments needed
• TypeError: can't define property "x": "obj" is not extensible
• TypeError: cyclic object value
• TypeError: invalid Array.prototype.sort argument
• TypeError: invalid arguments
• TypeError: invalid assignment to const "x"
• TypeError: property "x" is non-configurable and can't be deleted
• TypeError: setting a property that has only a getter
• TypeError: variable "x" redeclares argument
• URIError: malformed URI sequence
• Warning: -file- is being assigned a //# sourceMappingURL, but already has one
• Warning: 08/09 is not a legal ECMA-262 octal constant
• Warning: Date.prototype.toLocaleFormat is deprecated
• Warning: JavaScript 1.6's for-each-in loops are deprecated
• Warning: String.x is deprecated; use String.prototype.x instead
• Warning: expression closures are deprecated
• Warning: unreachable code after return statement
• JavaScript technologies overview
• Lexical grammar
• Enumerability and ownership of properties
• Iteration protocols
• Transitioning to strict mode
• Template literals
• Deprecated features
• ECMAScript 2015 support in Mozilla
• ECMAScript 5 support in Mozilla
• ECMAScript Next support in Mozilla
• Firefox JavaScript changelog
• New in JavaScript 1.1
• New in JavaScript 1.2
• New in JavaScript 1.3
• New in JavaScript 1.4
• New in JavaScript 1.5
• New in JavaScript 1.6
• New in JavaScript 1.7
• New in JavaScript 1.8
• New in JavaScript 1.8.1
• New in JavaScript 1.8.5
• Documentation:
• All pages index
• Methods index
• Properties index
• Pages tagged "JavaScript"
• JavaScript doc status
• The MDN project

• DSA with JS - Self Paced
• JS Tutorial
• JS Exercise
• JS Interview Questions
• JS Operator
• JS Projects
• JS Examples
• JS Free JS Course
• JS A to Z Guide
• JS Formatter

JavaScript TypeError – Invalid assignment to const “X”

This JavaScript exception invalid assignment to const occurs if a user tries to change a constant value. Const declarations in JavaScript can not be re-assigned or re-declared.

Error Type:

Cause of Error: A const value in JavaScript is changed by the program which can not be altered during normal execution. 

Example 1: In this example, the value of the variable(‘GFG’) is changed, So the error has occurred.

Output(in console):

Example 2: In this example, the value of the object(‘GFG_Obj’) is changed, So the error has occurred.

Please Login to comment...

Similar reads.

• Web Technologies
• JavaScript-Errors
• Discord Emojis List 2024: Copy and Paste
• Best Adblockers for Twitch TV: Enjoy Ad-Free Streaming in 2024
• PS4 vs. PS5: Which PlayStation Should You Buy in 2024?
• Best Mobile Game Controllers in 2024: Top Picks for iPhone and Android
• 15 Most Important Aptitude Topics For Placements [2024]

Improve your Coding Skills with Practice

What kind of Experience do you want to share?

Typeerror assignment to constant variable

Doesn’t know how to solve the “Typeerror assignment to constant variable” error in Javascript?

Don’t worry because this article will help you to solve that problem

In this article, we will discuss the Typeerror assignment to constant variable , provide the possible causes of this error, and give solutions to resolve the error.

What is Typeerror assignment to constant variable?

“Typeerror assignment to constant variable” is an error message that can occur in JavaScript code.

It means that you have tried to modify the value of a variable that has been declared as a constant.

When we try to reassign greeting to a different value (“Hi”) , we will get the error:

because we are trying to change the value of a constant variable.

How does Typeerror assignment to constant variable occurs ?

In JavaScript, constants are variables whose values cannot be changed once they have been assigned.

Here is an example :

In this example, we declared a constant variable age and assigned it the value 30 .

If you declare an object using the const keyword, you can still modify the properties of the object.

For example:

In this example, we declared a constant object person with two properties ( name and age ).

In this example, we declared a constant variable name and assigned it the value John .

Now let’s fix this error.

Typeerror assignment to constant variable – Solutions

Solution 1: declare the variable using the let or var keyword:.

Just like the example below:

Solution 2: Use an object or array instead of a constant variable:

If you need to modify the properties of a variable, you can use an object or array instead of a constant variable.

Solution 3: Declare the variable outside of strict mode:

Solution 4: use the const keyword and use a different name :, solution 5: declare a const variable with the same name in a different scope :.

But with a different value, without modifying the original constant variable.

You can create a new constant variable with the same name, without modifying the original constant variable.

So those are the alternative solutions that you can use to fix the TypeError.

In conclusion, in this article, we discussed   “Typeerror assignment to constant variable” , provided its causes and give solutions that resolve the error.

We’re happy to help you.

Go to list of users who liked

More than 3 years have passed since last update.

【React】TypeError: Assignment to constant variableの対処法

下記ソースを実行したときに、TypeError: Assignment to constant variableが発生してしまいました。 翻訳すると、「TypeError: 定数変数への代入」という内容でした。

定数に対して再度値を代入しようとしていたため、起きていたようです。 useEffect内で代入せず、useStateやuseReduverで値を管理するとよさそうです。

Go to list of comments

Register as a new user and use Qiita more conveniently

• You get articles that match your needs
• You can efficiently read back useful information
• You can use dark theme

• Stack Overflow for Teams Where developers & technologists share private knowledge with coworkers
• Advertising & Talent Reach devs & technologists worldwide about your product, service or employer brand
• OverflowAI GenAI features for Teams
• OverflowAPI Train & fine-tune LLMs
• Labs The future of collective knowledge sharing
• About the company Visit the blog

Collectives™ on Stack Overflow

Find centralized, trusted content and collaborate around the technologies you use most.

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

Get early access and see previews of new features.

UglifyJsPlugin : Uncaught (in promise) TypeError: Assignment to constant variable

Webapp build with webpack (framework used is vuejs, from a quick look that's not relevant here)

When webapp is in dev mode, no error thrown. When webapp is in production mode (built) an error is thrown : Uncaught (in promise) TypeError: Assignment to constant variable

In store's action.js file

Quick analyse

The error seems occurs when following function is called in a get with axios.

The error does not occur anymore when this code is replaced by

Do you have any idea why the error occurs in first place ?

EDIT : When isError404(error) is declared like : let isError404 = function(error){ ...

I don't have an error if I console.log(isError404(error)) before the if .

It seems after searching on the net that error could be cause by the package "uglifyjs-webpack-plugin": "^1.1.1", but I don't know how I can test and be sure.

Edit 2 : Webpack 3.12.0

• 1 There's not enough code in the question to tell what the problem is. –  Pointy Commented Sep 7, 2022 at 13:11
• @Pointy : I've added more code thanks –  Romain PORTIER Commented Sep 7, 2022 at 14:28
• why aren't you returning from the isError function? And could you provide your webpack config, please? –  Michele Viviani Commented Sep 7, 2022 at 14:41
• It's a bit hard to replicate it. The fastest answer and best practice that i can say is, for function assignment, use always const . Because you will never assign the variable again, and using const prevent that to. –  Michele Viviani Commented Sep 7, 2022 at 20:22
• @MicheleViviani Thank you for your answer ! The problem was link do UglifyJS plugin which was assigning a const with itself generating the error. –  Romain PORTIER Commented Sep 8, 2022 at 7:01

I found the origin of the error : https://github.com/mishoo/UglifyJS/issues/2843

Explanation :

If I understand the problem UglifyJsPlugin (1.1.1) uses a version of UglifyJS which create the error when reassigning a constant with itself.

This is caused when inline options is true (by default in this version).

Until package update the easiest workaround is to set uglifyJsPlugin's inline option to false in webpack configuration :

Your Answer

Reminder: Answers generated by artificial intelligence tools are not allowed on Stack Overflow. Learn more

Sign up or log in

Post as a guest.

Required, but never shown

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy .

Not the answer you're looking for? Browse other questions tagged javascript webpack vuejs2 promise uglifyjs or ask your own question .

• The Overflow Blog
• The hidden cost of speed
• The creator of Jenkins discusses CI/CD and balancing business with open source
• Featured on Meta
• Announcing a change to the data-dump process
• Bringing clarity to status tag usage on meta sites
• What does a new user need in a homepage experience on Stack Overflow?
• Feedback requested: How do you use tag hover descriptions for curating and do...
• Staging Ground Reviewer Motivation

Hot Network Questions

• Why do "modern" languages not provide argv and exit code in main?
• How many color information loss if I iterate all hue and value while keep saturation constant?
• Textile Innovations of Pachyderms: Clothing Type
• How long should a wooden construct burn (and continue to take damage) until it burns out (and stops doing damage)
• The head of a screw is missing on one side of the spigot outdoor
• Pólya trees counted efficiently
• Can population variance from multiple studies be averaged to use for a sample size calculation?
• What does こんなところ refer to here
• Are fuel efficiency charts available for mainstream engines?
• Generating function for A261041
• Question about word (relationship between language and thought)
• What was the typical amount of disk storage for a mainframe installation in the 1980s?
• Job suffering for the misdeeds of his ancestors
• Spin-Spin Correlation Function
• What qualifies as a Cantor diagonal argument?
• "With" as a function word to specify an additional circumstance or condition
• Starting with 2014 "+" signs and 2015 "−" signs, you delete signs until one remains. What’s left?
• What is the Kronecker product of two 1D vectors?
• What prevents random software installation popups from mis-interpreting our consents
• How cheap would rocket fuel have to be to make Mars colonization feasible (according to Musk)?
• What is the least number of colours Peter could use to color the 3x3 square?
• Romeo & Juliet laws and age of consent laws
• Preventing BEAST by using authorisation header instead of cookies
• Somebody used recommendation by an in-law – should I report it?

Navigation Menu

Search code, repositories, users, issues, pull requests..., provide feedback.

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly.

To see all available qualifiers, see our documentation .

• Notifications You must be signed in to change notification settings

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement . We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Uncaught (in promise) TypeError: Assignment to constant variable. in swagger.js:241 #74

dadaphl commented Aug 13, 2018

ricricucit commented Aug 13, 2018

Sorry, something went wrong.

ricricucit commented Mar 4, 2019

No branches or pull requests