Open ashelman-ec opened 1 year ago
I see this is the same as boilerplate issue #99.
I am too new to Javascript & hapi to submit a PR at this time, though might be competent enough in a couple months...
Hmm linting is broken and not sure how to fix it...
How is linting broken? Did you mean in your own project or while contributing to hapipal?
I mean, once I reached this part of the tutorial, npm run lint
failed, as below.
Note that, per the deprecation warnings at the top of this issue, I had modified package.json
and .eslintrc.json
from @hapi/eslint-plugin-hapi
to @hapi/eslint-plugin
. Not sure if that was the correct thing to do...
> npm run lint
> hapipal-boilerplate@3.0.0 lint
> eslint .
Oops! Something went wrong! :(
ESLint: 7.32.0
ESLint couldn't find the config "@hapi/eslint-plugin" to extend from. Please check that the name of the config is correct.
The config "@hapi/eslint-plugin" was referenced from the config file in "C:\Users\...\paldo-riddles\.eslintrc.json".
If you still have problems, please stop by https://eslint.org/chat/help to chat with the team.
Ok, thanks @ashelman-ec for the explanation. Not sure what's the problem though. I'd have to check for myself. I don't have much available bandwidth right now, so I'm not sure when I'll be able to do that.
Trying to follow the hapipal Getting Started tutorial, but ran into these issues:
npm init @hapipal
does not work on Windows, see today's comments in hapipal.com issue #72Manually editing
package.json
to replace"babel-eslint": "10.x.x"
with"@babel/eslint-parser": "7.x.x"
quiets one of the warnings (but I don't know whether this newer version has any breaking changes and will actually work correctly)But that still leaves the security vulnerabilities: