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
First of all, thank you for providing this fine utility. It's saved me a bunch of time. As for the feature request itself: I'd like to contribute a configuration option to allow removing all headers from the header.hbs file.
Currently, the output from the library is not usable in an Node.js ESM project due to issues described in #1226. As a workaround, we've resorted to running the output through a cli script to remove the headers. This allows eslint to alter the output to match our project's needs; adding the .js extensions where applicable.
For those interested, we use this script:
cd src
find . -path '**/generated/**.ts' -type f -exec sh -c 'for file; do sed -i "" "/tslint:disable/d" ${file} sed -i "" "/eslint-disable/d" ${file} sed -i "" "/@ts-ignore/d" ${file}done' sh {} +
Since the .js extension PR is open for quite some time, I figured why not allow for this relatively simple change instead until a more permanent stance is taken on the ESM support front. Are you open to such a PR?
The text was updated successfully, but these errors were encountered:
Hi @ferdikoomen,
First of all, thank you for providing this fine utility. It's saved me a bunch of time. As for the feature request itself: I'd like to contribute a configuration option to allow removing all headers from the header.hbs file.
Currently, the output from the library is not usable in an Node.js ESM project due to issues described in #1226. As a workaround, we've resorted to running the output through a cli script to remove the headers. This allows eslint to alter the output to match our project's needs; adding the
.js
extensions where applicable.For those interested, we use this script:
Since the
.js
extension PR is open for quite some time, I figured why not allow for this relatively simple change instead until a more permanent stance is taken on the ESM support front. Are you open to such a PR?The text was updated successfully, but these errors were encountered: