Skip to content
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

balena-lint --fix wiped files #80

Open
joshbwlng opened this issue Jul 9, 2021 · 0 comments
Open

balena-lint --fix wiped files #80

joshbwlng opened this issue Jul 9, 2021 · 0 comments
Labels

Comments

@joshbwlng
Copy link
Contributor

Version: 6.1.1

npx balena-lint --fix seems to have wiped a number of files clean after encountering a syntax error in one of the files:

> @balena/[email protected] lint-fix /home/josh/git/product-os/jellyfish-plugin-default
> balena-lint --fix lib test

SyntaxError: Expression expected. (28:2)
  26 |                  actions,
  27 |          }),
> 28 |  }
     |  ^
  29 | }
  30 |
    at e (/home/josh/git/product-os/jellyfish-plugin-default/node_modules/prettier/parser-typescript.js:1:322)
    at /home/josh/git/product-os/jellyfish-plugin-default/node_modules/prettier/parser-typescript.js:22:3248894
    at Object.parse (/home/josh/git/product-os/jellyfish-plugin-default/node_modules/prettier/parser-typescript.js:22:3248927)
    at Object.parse$a [as parse] (/home/josh/git/product-os/jellyfish-plugin-default/node_modules/prettier/index.js:13684:19)
    at coreFormat (/home/josh/git/product-os/jellyfish-plugin-default/node_modules/prettier/index.js:15215:16)
    at formatWithCursor$1 (/home/josh/git/product-os/jellyfish-plugin-default/node_modules/prettier/index.js:15455:14)
    at /home/josh/git/product-os/jellyfish-plugin-default/node_modules/prettier/index.js:60228:12
    at Object.format (/home/josh/git/product-os/jellyfish-plugin-default/node_modules/prettier/index.js:60248:12)
    at /home/josh/git/product-os/jellyfish-plugin-default/node_modules/@balena/lint/build/balena-lint.js:94:44
    at async Promise.all (index 89) {
  loc: { start: { line: 28, column: 2 } },
  codeFrame: '\x1B[0m \x1B[90m 26 |\x1B[39m \t\t\tactions\x1B[33m,\x1B[39m\x1B[0m\n' +
    '\x1B[0m \x1B[90m 27 |\x1B[39m \t\t})\x1B[33m,\x1B[39m\x1B[0m\n' +
    '\x1B[0m\x1B[31m\x1B[1m>\x1B[22m\x1B[39m\x1B[90m 28 |\x1B[39m \t}\x1B[0m\n' +
    '\x1B[0m \x1B[90m    |\x1B[39m \t\x1B[31m\x1B[1m^\x1B[22m\x1B[39m\x1B[0m\n' +
    '\x1B[0m \x1B[90m 29 |\x1B[39m }\x1B[0m\n' +
    '\x1B[0m \x1B[90m 30 |\x1B[39m\x1B[0m'
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @balena/[email protected] lint-fix: `balena-lint --fix lib test`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the @balena/[email protected] lint-fix script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
@joshbwlng joshbwlng added the bug label Jul 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant