-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
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
Use espower-typescript on non-testing code #73
Comments
@qsona Thank you and it looks good to me. Would you contribute to us? |
@qsona At first glance, it looks like working, but internally, ts-node has been registered twice. Line 13 in 049e1a8
TypeScript compiles one file twice, but in the second compilation, it does not change the JS code, so it looks like working as a result.
I do not know if it will not cause some problems when compiled multiple times in other cases. $ cp tsnodeconfig.ts tsnodeconfig.js
$ node --require ./tsnodeconfig.js src/index.ts |
If you want to bootstrap with your own ts-node like #66, you can add an option to not register the ts-node inside espower-typescript. PR welcome. |
@teppeis Oh thank you for your clarification! |
Hello,
I'd like to use power-assert on non-testing code (I mean it's normal server-side code) of TypeScript + Node.js. I couldn't find a proper way to do that (an example included in README of this project is using mocha) and am also very newbie about power-assert technology, so I randomly tried by myself and found a way.
Could you please review it? I'd like to contribute by creating a good example or adding usage to README so that other people who have same purpose can easily use this library.
Here's the example (somewhat working but maybe not ideal). Is it an intended or acceptable way?
https://github.com/qsona/power-assert-typescript-node-seed/pull/1/files
ts-node --require tsnodeconfig.ts
require('espower-typescript')
and call it withpattern
option intsnodeconfig.ts
The text was updated successfully, but these errors were encountered: