Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Property 'readonly' does not exist on type 'TagInputComponent'

See original GitHub issue

I’m submitting a … (check one with “x”)

[X] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request/question

Current behavior angular-cli ng build --aot --prod results in :: node_modules/ng2-tag-input/dist/modules/components/tag-input.template.html (13,6): Property ‘readonly’ does not exist on type ‘TagInputComponent’.

Expected behavior

successful build

Minimal reproduction of the problem with instructions (if applicable) ng build --aot --prod

What do you use to build your app? (SystemJS, Webpack, angular-cli, etc.). Please specify the version

    "@angular/cli": "^1.0.1",
    "@angular/compiler-cli": "next",
    "@angular/animations": "next",
    "@angular/common": "next",
    "@angular/compiler": "next",
    "@angular/core": "next",
    "@angular/flex-layout": "^2.0.0-beta.8",
    "@angular/forms": "next",
    "@angular/http": "next",
    "@angular/material": "^2.0.0-beta.2",
    "@angular/platform-browser": "next",
    "@angular/platform-browser-dynamic": "next",
    "@angular/router": "next",

Angular version: angular 4.2.0-rc.0

ng2-tag-input version:

^1.2.9

build

Issue Analytics

State:
Created 6 years ago
Reactions:1
Comments:14 (6 by maintainers)

Top GitHub Comments

1reaction

acuntexcommented, Jun 1, 2017

The bug is in “tag-input.template.html”: Since you removed the property readonly in TagInputComponent in commit b90801d94b809ee7ec64f522e48f3f44e1602db9 (May 24th 2017), AOT cannot bind to any “readonly” property thus breaking AOT-support

1reaction

bfan1256commented, May 27, 2017

I am having the same problem, I did not use the readonly property and it still cannot build.

Top Results From Across the Web

React: Property 'X' does not exist on type 'Readonly<{}>'

To solve the error, use the generic on the React.Component class to type the props or state objects of the class. property value...

Property does not exist on type Readonly { } - Stack Overflow

I am getting the following error: "Property 'items' does not exist on type 'Readonly<{}>'." and "Property 'value' does not exist on type ' ......

react-tag-input - npm

React tags is a fantastically simple tagging component for your React projects. Latest version: 6.8.1, last published: 4 months ago.

Solved - Property 'X' does not exist on type 'Readonly<{}>' in ...

This error occurs when we access a prop or state property that we have not explicitly given a type inside the React class...

property 'children' does not exist on type 'intrinsicattributes

Overload 1 of 2, '(props: DraggableProps | Readonly): Draggable', gave the following error. Type '{ children: ReactNode; key: number; }' is not assignable...