You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that with the new build process (the one that leverages simply on typescript project feature), the webpack compilation in the td-tools package is skipped. In theory, this would cause the inability to use the package https://www.npmjs.com/package/@node-wot/td-tools outside of Node.js. I wondering if anybody noticed, @danielpeintner@egekorkan.
The text was updated successfully, but these errors were encountered:
I noticed that with the new build process (the one that leverages simply on typescript project feature), the webpack compilation in the td-tools package is skipped
I am definitely not aware that td-tools is skipped.
What do you mean by "new build process" ? Am I missing something here?
I while ago we used the npm workspaces approach when building the whole code base. In practice, doing a npm run build implied that npm run the same command in all packages iteratively. For the td-tools package, the build script does a typescript build and then calls webpack. The new approach uses tsc -b && npm run build -w packages/browser-bundle, without calling the buildscript inside td-tools. I noticed that td-tools is also exposed inside the browser bundle so probably not many people use it as a direct dependency... but still it should be possible to use it as it is in browsers too.
I noticed that with the new build process (the one that leverages simply on typescript project feature), the webpack compilation in the td-tools package is skipped. In theory, this would cause the inability to use the package https://www.npmjs.com/package/@node-wot/td-tools outside of Node.js. I wondering if anybody noticed, @danielpeintner @egekorkan.
The text was updated successfully, but these errors were encountered: