chiefmikey/mikey-pro

Lint and format style guide

mikey-pro's Issues

Replace or update plugins using Trim <0.0.3

@stylelint
postcss-markdown
remark
remark-parse*
https://github.com/docs/remark-parse-no-trim

remark-message-control
unified-message-control*

feature(.env): add support

feature(web): create mikey-pro.com landing page

[Bug]: Cannot read property 'markers' of undefined

Contact Details

[email protected]

What happened?

When working with HTML, ESLint will look for closing tags and auto format to include them. On this action, an error is thrown in regards to 'markers' being a property of an undefined object. ESLint does not crash or go down but the error should be fixed.

Version

1.4.2

What browsers are you seeing the problem on?

Chrome

Relevant log output

[Error - 8:41:18 AM] ESLint stack trace:
[Error - 8:41:18 AM] TypeError: Cannot read property 'markers' of undefined
Occurred while linting /Users/Mikl/Dropbox/dev/apps/chiefmikey/README.html:1
    at checkCommentForSpace (/Users/Mikl/Dropbox/dev/apps/chiefmikey/node_modules/eslint/lib/rules/spaced-comment.js:336:49)
    at Array.forEach (<anonymous>)
    at Program (/Users/Mikl/Dropbox/dev/apps/chiefmikey/node_modules/eslint/lib/rules/spaced-comment.js:378:68)
    at /Users/Mikl/Dropbox/dev/apps/chiefmikey/node_modules/eslint/lib/linter/safe-emitter.js:45:58
    at Array.forEach (<anonymous>)
    at Object.emit (/Users/Mikl/Dropbox/dev/apps/chiefmikey/node_modules/eslint/lib/linter/safe-emitter.js:45:38)
    at NodeEventGenerator.applySelector (/Users/Mikl/Dropbox/dev/apps/chiefmikey/node_modules/eslint/lib/linter/node-event-generator.js:293:26)
    at NodeEventGenerator.applySelectors (/Users/Mikl/Dropbox/dev/apps/chiefmikey/node_modules/eslint/lib/linter/node-event-generator.js:322:22)
    at NodeEventGenerator.enterNode (/Users/Mikl/Dropbox/dev/apps/chiefmikey/node_modules/eslint/lib/linter/node-event-generator.js:336:14)
    at CodePathAnalyzer.enterNode (/Users/Mikl/Dropbox/dev/apps/chiefmikey/node_modules/eslint/lib/linter/code-path-analysis/code-path-analyzer.js:711:23)

Code of Conduct

• I agree to follow this project's Code of Conduct

feature(overrides): separate configs

currently all overrides and relevant packages are loaded on init
need to separate less common overrides to their own configs and package imports
have an all option to load everything still

feature(shell): add support

Bourne shell, bash, zsh, etc.