Comments (4)
Hmmm. I do see "dom-expressions": "^0.19.10",
in devDependencies
. 🤔
from dom-expressions.
Seems like that's the issue: because lit-dom-expressions
types depend on dom-expression
types, then dom-expressions
needs to be a dependency
instead of devDependency
.
Strange, I know, but otherwise TS users get the error. I think it's OK to have an extra dependency installed on the developer's file system just for the types.
This is discussed somewhere in TypeScript issues. Basically dom-expressions
can be left as a devDependency
only if the lit-dom-expressions
does not re-export or need to expose any of dom-expressions
types.
For example, if you export something like
import type {Foo} from 'some-package'
export class Bar extends Foo {...}
then some-package
needs to be a dependency
because otherwise Foo
will not be visible for the end user, but Foo
needs to be visible for the end user in order for the Bar
class to typed properly.
from dom-expressions.
PR: #26
from dom-expressions.
This will be resolved in v0.20.0.
from dom-expressions.
Related Issues (20)
- Cannot use `ref` for `Tagged Template`/`lit-dom-expressions` HOT 1
- Closing tag omission in dom `transformElement()` is broken with table/tbody HOT 2
- Ability to use web-components as component HOT 5
- wrong markup structure after omitting closing tags HOT 1
- Feature: symbols for JSX SSR
- Additional HTML closing tag omission HOT 1
- Ability to hide/show element on DOM using solid-js hypserscript
- Can't use `this` on prop function HOT 1
- bug: tagged template literals error when dynamic tag and quoted text as children
- Is it possible to optimize `style.text` to be like `style_text`? HOT 3
- `/* @once */` seems to work only for first child of object HOT 7
- Incorrect TypeScript definition for `http-equiv` and `accept-charset` attributes
- Incompatibility between Solid's markers and nginx Server Side Includes (SSI) HOT 5
- Is it possible to bind event to rootElement ? HOT 2
- ReferenceError: ogComplete is not defined HOT 1
- [html] top level <style> causes TypeError: Cannot read properties of undefined (reading 'firstChild')
- [html] empty html template causes TypeError: Cannot read properties of undefined (reading 'name')
- `o[1] is not a function`
- There is no definition of `media` property in interface `MetaHTMLAttributes`
- Bug in generic types for universal render target? HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from dom-expressions.