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 assume here it is on purpose, right @erossignon?
Yes, having "rootdir": ".", dist:"dist" will cause ts file in src to go to dist/src and test to dist/test/.
The benefit is that the same tsconfig.json file is used for eslinting (in VSCode) the src and tst files ... It also allows us to check the syntax of the test file during the tsc -b phase.
the downside is that generated files are not stored in the dist folder anymore but one level below.
In our setup, it does not really make sense to compile test files into the dist folder, for two reasons:
It pollutes the distributed npm packages with files that will never be used
Tests are executed using ts-node
I think that also opc-ua binding should follow the same setup of other packages.
In our setup, it does not really make sense to compile test files into the dist folder, for two reasons:
I think that also opc-ua binding should follow the same setup of other packages.
Originally posted by @relu91 in #598 (comment)
The text was updated successfully, but these errors were encountered: