$ uname -a Darwin eon 17.7.0 Darwin Kernel Version 17.7.0: Thu Jun 21 22:53:14 PDT 2018; root:xnu-4570.71.2~1/RELEASE_X86_64 x86_64 $ node --version v10.11.0 $ yarn test yarn run v1.10.1 $ yarn lint && yarn test-only $ sucrase-node script/lint.ts > ./node_modules/.bin/tsc --project . --noEmit [...] > ./node_modules/.bin/eslint './integrations/webpack-object-rest-spread-plugin/src/**/*.ts' [...] ERROR: /Users/raylu/src/sucrase/integrations/webpack-loader/src/index.ts[7, 28]: This assertion is unnecessary since it does not change the type of the expression. Unhandled error: Error: Command failed: ./node_modules/.bin/tslint --project ./integrations/webpack-loader
# Don't do feature branch builds; we only need one build per PR. branches: only: - "master"
nycwhich locally gives me
nyc └─┬ /usr/bin/node /usr/share/yarn/bin/yarn.js test-only │ 83.75 % Lines └─┬ /usr/bin/node /home/raylu/src/sucrase/node_modules/.bin/mocha ./test/**/*.ts │ 83.75 % Lines └── /usr/bin/node /home/raylu/src/sucrase/node_modules/mocha/bin/_mocha --require sucrase/register --require source-map-support/register ./test/**/*.ts 83.75 % Lines
I'm trying debug my TS Node app, where I compile JS with sucrase.
But it is not working.
The VS Code do not stop on the break points.
Looking for a fix in the web, I find some texts saying I need a sourceMap...
Using TS libs, it created tsconfig.json, but Sucrase do not created this.
Some tip that how I can debbug in VS Code?]
Hey there, I plan on adding some functionality to the cli.
Any concerns with these changes?
@Delerme Hey! Sorry for taking a while to respond. JSX extension support has two PRs open, so I'll try to get that merged so you don't need to implement it.
For the specific files, what was your thought for the location of the destination JS files? I think it's probably best to follow babel-cli (https://babeljs.io/docs/en/babel-cli) and print to stdout or to
--out-file, and only process one file per CLI invocation in that case. FWIW I usually end up using webpack or
sucrase/register in my projects rather than ever invoking the CLI directly, but I realize build systems can vary quite a bit.