Skip to content

Build: Introduce local eslint rule for storybook node logger #31655

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

Draft
wants to merge 2 commits into
base: next
Choose a base branch
from

Conversation

yannbf
Copy link
Member

@yannbf yannbf commented Jun 3, 2025

Closes #

What I did

Checklist for Contributors

Testing

The changes in this PR are covered in the following automated tests:

  • stories
  • unit tests
  • integration tests
  • end-to-end tests

Manual testing

This section is mandatory for all contributions. If you believe no manual test is necessary, please state so explicitly. Thanks!

Documentation

  • Add or update documentation reflecting your changes
  • If you are deprecating/removing a feature, make sure to update
    MIGRATION.MD

Checklist for Maintainers

  • When this PR is ready for testing, make sure to add ci:normal, ci:merged or ci:daily GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found in code/lib/cli-storybook/src/sandbox-templates.ts

  • Make sure this PR contains one of the labels below:

    Available labels
    • bug: Internal changes that fixes incorrect behavior.
    • maintenance: User-facing maintenance tasks.
    • dependencies: Upgrading (sometimes downgrading) dependencies.
    • build: Internal-facing build tooling & test updates. Will not show up in release changelog.
    • cleanup: Minor cleanup style change. Will not show up in release changelog.
    • documentation: Documentation only changes. Will not show up in release changelog.
    • feature request: Introducing a new feature.
    • BREAKING CHANGE: Changes that break compatibility in some way with current major version.
    • other: Changes that don't fit in the above categories.

🦋 Canary release

This PR does not have a canary release associated. You can request a canary release of this pull request by mentioning the @storybookjs/core team here.

core team members can create a canary release here or locally with gh workflow run --repo storybookjs/storybook canary-release-pr.yml --field pr=<PR_NUMBER>

Greptile Summary

Introduces a new ESLint rule 'enforce-node-logger' to ensure consistent usage of Storybook's node-logger instead of console methods throughout the codebase.

  • Added enforce-node-logger.js rule implementation with auto-fix capabilities for both direct console usage and logger assignments
  • Configured rule in code/.eslintrc.js to target specific TypeScript files with 'error' severity
  • Rule automatically manages imports and variable declarations while providing clear error messages
  • Applied to core and lib directories while excluding test/spec files and logger modules
  • Added comprehensive documentation in README.md explaining the rule's purpose and behavior

@yannbf yannbf self-assigned this Jun 3, 2025
@yannbf yannbf added build Internal-facing build tooling & test updates ci:normal labels Jun 3, 2025
Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

4 file(s) reviewed, 5 comment(s)
Edit PR Review Bot Settings | Greptile

@@ -0,0 +1,111 @@
module.exports = {
meta: {
type: 'problem',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

logic: Rule type should be 'suggestion' since this is a code style preference, not a runtime error

Suggested change
type: 'problem',
type: 'suggestion',

Comment on lines +74 to +78
CallExpression(node) {
if (
node.callee.type === 'MemberExpression' &&
node.callee.object.name === 'console'
) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

logic: Missing check for computed properties (e.g. console['log']). This allows bypassing the rule

Comment on lines +89 to +102
// Add import if missing
if (!loggerImported) {
if (importNode) {
const last = importNode.specifiers[importNode.specifiers.length - 1];
fixes.push(fixer.insertTextAfter(last, ', logger'));
} else {
fixes.push(
fixer.insertTextBeforeRange(
[0, 0],
"import { logger } from 'storybook/internal/node-logger';\n"
)
);
}
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

style: Duplicate code block from lines 54-66. Extract to a shared helper function

Comment on lines +177 to +183
excludedFiles: [
'core/node-logger/**/*.ts',
'core/client-logger/**/*.ts',
'**/*.test.*',
'**/*.spec.*',
'**/*.mockdata.*',
],
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

style: Redundant exclusion of test/spec files - already excluded in files pattern above with !/.test. and !/.spec.

Suggested change
excludedFiles: [
'core/node-logger/**/*.ts',
'core/client-logger/**/*.ts',
'**/*.test.*',
'**/*.spec.*',
'**/*.mockdata.*',
],
excludedFiles: [
'core/node-logger/**/*.ts',
'core/client-logger/**/*.ts',
'**/*.mockdata.*',
],

Comment on lines +13 to +14
- Automatically add `import { logger } from 'node-logger'` when needed
- **Why**: Promotes consistent logging across the codebase using Storybook's logger. The logger has log level and tracking capabilities, which is important for debugging purposes and keeps the user experience consistent as well.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

style: The 'Why' point is formatted inconsistently with the bullet points above it (using bold markdown instead of a dash prefix)

Copy link

nx-cloud bot commented Jun 3, 2025

View your CI Pipeline Execution ↗ for commit f93449e.

Command Status Duration Result
nx run-many -t build --parallel=3 ✅ Succeeded 1m 26s View ↗

☁️ Nx Cloud last updated this comment at 2025-06-03 16:50:05 UTC

Base automatically changed from yann/use-logger-everywhere to valentin/monorepo-enhancements June 4, 2025 06:09
Base automatically changed from valentin/monorepo-enhancements to next June 10, 2025 14:55
@valentinpalkovic valentinpalkovic marked this pull request as draft June 16, 2025 10:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build Internal-facing build tooling & test updates ci:normal
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant