We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Discussion - #891
I'm trying build Lit Element examples using wmr. The ts examples play nicely - the ts ones fail with the @ of the decorator
https://lit.dev/playground/#sample=examples/full-component
Is your feature request related to a problem? Please describe.
./public\motion-todos.ts - Unexpected character '@' (./motion-todos.ts:26:1) 24 | 25 | > 26 | @customElement('motion-todos') | ^ 27 | export class MotionTodos extends LitElement {constructor(...args) { super… 28 | static __initStatic() {this.styles = styles} 29 |
alangpierce/sucrase#330
Work around Use the long form customElements.define('motion-todos',MotionTodos)
customElements.define('motion-todos',MotionTodos)
define the properties the old skool js way
Describe the solution you'd like It would be great it it just worked ;-)
The text was updated successfully, but these errors were encountered:
I created a minimal example, but as previously stated the decorators do not work. I have to use the long form:
https://github.com/rodydavis/lit-wmr
Branch with decorators:
https://github.com/rodydavis/lit-wmr/tree/ts-decorators
Sorry, something went wrong.
No branches or pull requests
Discussion - #891
I'm trying build Lit Element examples using wmr. The ts examples play nicely - the ts ones fail with the @ of the decorator
https://lit.dev/playground/#sample=examples/full-component
Is your feature request related to a problem? Please describe.
alangpierce/sucrase#330
Work around
Use the long form
customElements.define('motion-todos',MotionTodos)
define the properties the old skool js way
Describe the solution you'd like
It would be great it it just worked ;-)
The text was updated successfully, but these errors were encountered: