-
Notifications
You must be signed in to change notification settings - Fork 9
Defects of the current npm package #29
Comments
@hungtcs I was going to create such an issue about mxClient that I cannot use on my project. I currently don't know if we require a new 'factory' package to solve the issues. The current definitions are full of |
@hungtcs hi, I know you are working on a new solution to fix this issue in the @typed-mxgraph organization, I will go back to you soon on that topic. |
Hi @tbouffard , I already publish a new version(1.0.4) to npm. |
@tbouffard I created a new version in @typed-mxgraph to suitable for the official package, the current way is cumbersome to use, the goal of @typed-mxgraph/typed-mxgraph is reduce user configuration. But so far, I haven't done enough testing to using on production environment |
@hungtcs thanks, you rock (as always)! |
I have recently seen this new package. I plan to have a look at it on this week. |
Thanks @tbouffard. |
1.
typeRoots
only detect subfoldersfor instance:
mxClient
is declared innode_modules/mxgraph-type-definitions/mxClient.d.ts
, but typescript can not detect this, packages in@types/*
not have this problem.Possible solution:
mxgraph-type-definitions
package under a npm organization.2. Should we create a factory package to match
mxgraph-type-definitions
Simple implementation:
The text was updated successfully, but these errors were encountered: