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

npm run test in freshly created app fails with error #37

Open
YJDoc2 opened this issue May 19, 2024 · 0 comments
Open

npm run test in freshly created app fails with error #37

YJDoc2 opened this issue May 19, 2024 · 0 comments

Comments

@YJDoc2
Copy link

YJDoc2 commented May 19, 2024

I created an ink app with npx create-ink-app my-ink-cli . After the setup was done, I cd into the example dir, and ran npm run test . That gave the following error -

> npm run test

> [email protected] test
> prettier --check . && xo && ava

Checking formatting...
All matched files use Prettier code style!
TypeError: Cannot read properties of undefined (reading 'getAllComments')
Occurred while linting /ink-example/test.js:1
Rule: "unicorn/expiring-todo-comments"
    at Object.Program (/ink-example/node_modules/eslint/lib/rules/no-warning-comments.js:193:45)
    at Program (/ink-example/node_modules/eslint-plugin-unicorn/rules/expiring-todo-comments.js:511:10)
    at /ink-example/node_modules/eslint-plugin-unicorn/rules/utils/rule.js:39:18
    at ruleErrorHandler (/ink-example/node_modules/eslint/lib/linter/linter.js:1076:28)
    at /ink-example/node_modules/eslint/lib/linter/safe-emitter.js:45:58
    at Array.forEach (<anonymous>)
    at Object.emit (/ink-example/node_modules/eslint/lib/linter/safe-emitter.js:45:38)
    at NodeEventGenerator.applySelector (/ink-example/node_modules/eslint/lib/linter/node-event-generator.js:297:26)
    at NodeEventGenerator.applySelectors (/ink-example/node_modules/eslint/lib/linter/node-event-generator.js:326:22)
    at NodeEventGenerator.enterNode (/ink-example/node_modules/eslint/lib/linter/node-event-generator.js:340:14)

Note : I have truncated the path in error log, it is not actually installed at / .

I expected that the fresh install should be in working condition including tests. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant