• Draft comment:
  Changing the default export to only export the format function is intentional, but please ensure that documentation and examples are updated accordingly.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
  The comment is asking the PR author to ensure that documentation and examples are updated, which violates the rule against asking the author to ensure things are done. It does not provide a specific suggestion or ask for a specific test to be written.

• Draft comment:
  The 'main' and 'types' fields still point to lib/index.js and lib/index.d.ts which are now deleted. Please ensure the build system regenerates these files appropriately or update these entries.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

• Draft comment:
  Test updated to check default export equals format; verify that removal of analyze export from default export does not affect users needing analyze as a named export.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

• Draft comment:
  Adding 'test/fixtures' to .prettierignore is fine, but ensure that this exclusion doesn't hide intentional formatting tests.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

• Draft comment:
  Adding 'test/fixtures' to the ignore list prevents accidental formatting of fixture files. This is appropriate.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
  This comment is purely informative and does not provide any actionable feedback or suggestions. It simply states a fact about the change, which violates the rule against making purely informative comments.

• Draft comment:
  Renaming the 'fix' script to separate 'format' and 'lint' commands and removing unused devDependencies (Babel packages and eslint-config-kentcdodds) cleans up the project. Ensure users update any CI or developer scripts accordingly.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
  The comment is informative and suggests ensuring that users update their CI or developer scripts, which is not allowed. It doesn't provide a specific code suggestion or ask for a specific test to be written.

• Draft comment:
  Default export now returns only the 'format' function, which fixes the regression. Users needing 'analyze' should import it as a named export.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
  This comment is purely informative, explaining a change in the export structure of a module. It doesn't provide a suggestion, ask for confirmation, or highlight a potential issue. It simply states what the change is and how users should adapt to it.

• Draft comment:
  The test now confirms that the default export equals the 'format' function. This aligns with the intended export change.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
  This comment is purely informative, as it simply states that the test confirms the intended export change. It does not provide any actionable feedback or suggestions for improvement.

• Draft comment:
  Typo: In the docstring for the analyze function (line 42), it currently says "To options parameter". Please change 'To' to 'The' for correctness.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

Reviewing files that changed from the base of the PR and between 5335c10 and a537bcb.

• lib/index.js.map is excluded by !**/*.map
• lib/types.js.map is excluded by !**/*.map
• lib/utils.js.map is excluded by !**/*.map
• yarn.lock is excluded by !**/yarn.lock, !**/*.lock

• .gitignore (1 hunks)
• .prettierignore (1 hunks)
• lib/index.d.ts (0 hunks)
• lib/index.js (0 hunks)
• lib/tsconfig.tsbuildinfo (0 hunks)
• lib/types.d.ts (0 hunks)
• lib/types.js (0 hunks)
• lib/utils.d.ts (0 hunks)
• lib/utils.js (0 hunks)
• package.json (1 hunks)
• src/index.ts (1 hunks)
• test/index.spec.ts (1 hunks)

• lib/types.js
• lib/tsconfig.tsbuildinfo
• lib/index.d.ts
• lib/utils.d.ts
• lib/types.d.ts
• lib/index.js
• lib/utils.js

.gitignore (1)

2-5: Looks good: Reorganized .gitignore entries.

The changes properly reorganize the ignore patterns and add the lib directory to the ignore list, which aligns with the removal of the lib directory's source and declaration files in this PR. The more generic .*cache pattern is also a good improvement over the specific .eslintcache.

.prettierignore (1)

2-2: LGTM: Added test/fixtures to prettierignore.

Adding the test/fixtures directory to the ignore list is appropriate, as test fixtures often contain intentionally formatted code that shouldn't be modified by Prettier.

src/index.ts (1)

426-426:

Details

✅ Verification successful

Simplified module export to directly expose format function.

This change correctly addresses the regression by simplifying the default export to only expose the format function directly, rather than an object containing both format and analyze. This matches the PR objective to fix the export entry regression.

---

🏁 Script executed:

#!/bin/bash
# Verify how the module is imported in the project and downstream dependencies

# Check for imports in the test files to see if they've been updated
grep -r "from 'prettier-eslint'" --include="*.ts" --include="*.js" ./test

Length of output: 225

---

🏁 Script executed:

#!/bin/bash
# Display the first 200 lines of test/index.spec.ts to inspect import usage
sed -n '1,200p' test/index.spec.ts

# Display the first 200 lines of test/utils.spec.ts to inspect import usage
sed -n '1,200p' test/utils.spec.ts

Length of output: 10579

---

🏁 Script executed:

#!/bin/bash
# Verify named exports and default export in src/index.ts
rg -n "export .*analyze" src/index.ts
rg -n "export default" src/index.ts | head -n 20

Length of output: 185

---

Default export now correctly exposes format

The module’s default export in src/index.ts has been simplified to point directly at the format function. Named exports such as analyze remain untouched, and the tests in test/index.spec.ts confirm that the default import (prettierESLint) equals format. No further changes are required.

test/index.spec.ts (2)

32-32: Updated test to match new export structure.

The test has been correctly updated to verify that prettierESLint is now directly the format function, rather than an object with a format property. This change properly aligns with the updated export in src/index.ts.

---

34-34: Removed redundant closing brace.

The closing brace of the test block has been adjusted to match the removal of the test for the analyze function export, which is consistent with the simplification of the module's exports.

• Draft comment:
  The interface still extends typeof format and includes both format and analyze, although the default export is now just format. Consider clarifying/documenting this discrepancy or possibly updating the interface to reflect the new export pattern.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 20% vs. threshold = 50%
  Since this is a new file, all code is changed code. The comment points out a potential design issue in the type definitions. However, without seeing the actual implementation and export patterns in the referenced files, I can't verify if this is actually a problem or if it's intentionally designed this way. The comment is speculative and asks for clarification rather than pointing out a definite issue.
  I might be too quick to dismiss this - there could be a real type safety issue here that needs addressing. The interface structure does look unusual.
  While the structure is unusual, without seeing the implementation files, we can't know if this is actually incorrect. The comment is asking for clarification rather than pointing out a definite problem.
  Delete the comment because it's speculative and asks for clarification rather than identifying a clear issue that needs fixing.

• Draft comment:
  Default export now directly returns the format function. This change is consistent with the fix but make sure the documentation clearly states that only format is exported as default.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
  The comment is informative and suggests ensuring documentation clarity, which is not allowed. It doesn't provide a specific code suggestion or ask for a test to be written.

• Draft comment:
  Updated main and types to the new entry points (index.js/index.d.ts) is good. Ensure that downstream consumers are aware of the breaking change in the default export.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
  This comment is asking the PR author to ensure that downstream consumers are aware of a breaking change. It doesn't provide a specific code suggestion or ask for a specific test to be written. It seems to be more of a reminder or a caution, which violates the rule against asking the author to ensure something is tested or verified.

• Draft comment:
  The default export now exports only the format function. This aligns with the intended fix. Double-check that the removal of analyze from the default export is clearly noted in the changelog.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
  The comment is asking the PR author to double-check that a change is noted in the changelog, which violates the rule against asking the author to double-check things. The first part of the comment is purely informative, stating what the default export now does. Overall, this comment should be removed.

• Draft comment:
  Test now expects the default export to be the format function. Verify that all tests remain valid with the updated export for both default and named exports.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
  The comment is asking the PR author to verify that all tests remain valid with the updated export. This falls under the rule of not asking the author to ensure the behavior is intended or to make sure their change is tested. Therefore, this comment should be removed.

• Draft comment:
  Consider using the nullish coalescing operator (??) instead of || for boolean options in getESLintApiOptions to avoid overriding explicit false values.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

• Draft comment:
  Pass the promise returned by format() directly to rejects.toThrow instead of wrapping it in a function.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

• Draft comment:
  Similarly, use the promise from format() directly with rejects.toThrow for the prettier module error test.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

• Draft comment:
  Verify that the PrettierESLint interface accurately reflects the public API now that the default export is just the format function with attached properties.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
  The comment is asking the PR author to verify the accuracy of the PrettierESLint interface after a change in the default export. This falls under asking the author to confirm or verify something, which is against the rules.

• Draft comment:
  The maintainer entry 'JounQin admin@1stg.me (https://www.1stG.me)' appears to have inconsistent capitalization (e.g. 'JounQin' and the URL '1stG.me' vs the email domain '1stg.me'). Please double-check if this is intentional or a typographical error.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

• Draft comment:
  Typographical error: Replace 'To options parameter of format' with 'The options parameter of format'.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

Reviewing files that changed from the base of the PR and between a537bcb and 5b8c4af.

• lib/index.js.map is excluded by !**/*.map
• lib/types.js.map is excluded by !**/*.map
• lib/utils.js.map is excluded by !**/*.map
• yarn.lock is excluded by !**/yarn.lock, !**/*.lock

• .changeset/perfect-carrots-repair.md (1 hunks)
• .gitignore (1 hunks)
• .prettierignore (1 hunks)
• index.d.ts (1 hunks)
• index.js (1 hunks)
• lib/index.d.ts (0 hunks)
• lib/index.js (0 hunks)
• lib/tsconfig.tsbuildinfo (0 hunks)
• lib/types.d.ts (0 hunks)
• lib/types.js (0 hunks)
• lib/utils.d.ts (0 hunks)
• lib/utils.js (0 hunks)
• package.json (2 hunks)
• src/index.ts (1 hunks)
• test/index.spec.ts (1 hunks)

• lib/types.js
• lib/index.d.ts
• lib/tsconfig.tsbuildinfo
• lib/types.d.ts
• lib/index.js
• lib/utils.js
• lib/utils.d.ts

• .changeset/perfect-carrots-repair.md
• index.js
• package.json

• .prettierignore
• .gitignore
• test/index.spec.ts
• src/index.ts

index.d.ts (1)

1-1: Verify import path and module resolution
The import statement

import {analyze, format} from './lib/index.js'

must resolve correctly in both TS and at runtime. Please confirm that:

1. lib/index.js (and its accompanying .d.ts) will be included in the published package.
2. Your tsconfig.json (e.g., moduleResolution, allowJs, resolveJsonModule) supports importing .js files from a .d.ts.

🧰 Tools

🪛 ESLint

[error] 1-1: Unable to resolve path to module './lib/index.js'.

(import-x/no-unresolved)

• Draft comment:
  The interface extends the Format type and then redefines both 'analyze' and 'format'. Confirm this duplication is intended.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 10% vs. threshold = 50%
  The comment is technically correct - there is duplication since Format (typeof format) is being extended and format is also explicitly declared. However, this appears to be intentional TypeScript type definition structure, possibly for better type documentation or IDE support. The comment just asks for confirmation without suggesting a clear improvement.
  The duplication might serve a purpose in TypeScript type definitions that I'm not aware of. Maybe it's a common pattern.
  Even if the duplication serves a purpose, the comment doesn't suggest any concrete improvement - it just asks for confirmation, which violates our rules.
  Delete the comment because it merely asks for confirmation without suggesting a clear improvement, which violates our commenting rules.

• Draft comment:
  Using type aliases (like 'Fs' and 'Prettier') improves clarity. Verify that these aliases match all expected fs and prettier members in downstream tests.
• Reason this comment was not posted:
  Confidence changes required: 30% <= threshold 50%
  None

• Draft comment:
  The order in the 'files' array changed with 'index.d.ts' now preceding 'index.js'. Confirm that this reordering aligns with intended packaging behavior.
• Reason this comment was not posted:
  Confidence changes required: 30% <= threshold 50%
  None

• Draft comment:
  Confirm that extending 'Format' and then re-declaring 'format' is intended for a callable export with extra properties.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

• Draft comment:
  Using a type alias for 'fs' (as 'Fs') improves consistency; consider a similar approach for ESLint in ESLintMock if desired.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

• Draft comment:
  The ordering in the 'files' array has been changed (index.d.ts now comes before index.js). Confirm that this ordering meets the intended export resolution.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

• Draft comment:
  The interface extends 'Format' (a callable) and then declares a 'format' property. Ensure this duplication is intentional to support both call signature and property access.
• Reason this comment was not posted:
  Confidence changes required: 50% <= threshold 50%
  None

• Draft comment:
  Using type alias (Fs) for node:fs clarifies this extension. Confirm consistency with other similar type definitions in the project.
• Reason this comment was not posted:
  Confidence changes required: 20% <= threshold 50%
  None

• Draft comment:
  The reordering in the 'files' array is minor. Verify that changing the order of 'index.d.ts' and 'index.js' is intentional and doesn't affect packaging.
• Reason this comment was not posted:
  Confidence changes required: 10% <= threshold 50%
  None

• Draft comment:
  The namespace 'prettierESLint' is used to contain the callable interface and is later re-exported with the same name. While this pattern is valid, sharing the same name for both the namespace and the exported constant could be confusing for consumers. Consider clarifying with documentation or using a distinct namespace name.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

• Draft comment:
  Using type aliases (e.g. 'type Fs = typeof fs' and 'type Prettier = typeof prettier') improves readability compared to inline '(typeof X)'. Removal of the 'prettier-ignore' comments suggests improved formatting. Ensure this aligns with your project’s style guidelines.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

• Draft comment:
  The order of file entries in the 'files' array has been altered (swapping 'index.js' and 'index.d.ts'). Although order typically does not affect published files, verify that this reordering is intentional and does not impact any downstream tooling in your build/publishing process.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

• Draft comment:
  Extending a function type via alias 'Format' is unusual. Confirm that creating the interface this way preserves expected callable behavior.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 50% <= threshold 50%
  The comment is asking the author to confirm that the behavior is preserved, which is against the rules. However, it also points out an unusual practice, which could be useful for the author to reconsider their approach. The comment could be rephrased to suggest a review of the approach without asking for confirmation.

• Draft comment:
  Use of 'export =' for CommonJS export is correct, but double-check that namespace merging and consumer syntax remain unaffected.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
  The comment is asking the PR author to double-check the effects of using export = on namespace merging and consumer syntax. This falls under the rule of not asking the author to double-check things or ensure behavior is intended. Therefore, this comment should be removed.

• Draft comment:
  Explicitly creating the type alias 'Fs' improves clarity—ensure consistency with other similar type aliases in the codebase.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

• Draft comment:
  Reordering files (index.d.ts before index.js) is minor but verify that module resolution in consuming projects remains unaffected.
• Reason this comment was not posted:
  Confidence changes required: 30% <= threshold 50%
  None

• Draft comment:
  Namespace 'prettierESLint' now wraps the export types. Confirm that this structure mirrors the runtime export.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

• Draft comment:
  Interface 'PrettierESLint' extends the function type correctly. Consider adding brief JSDoc for clarity.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

• Draft comment:
  Using a type alias ('Fs') for 'typeof fs' improves clarity in FsMock. This refactor enhances maintainability.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

• Draft comment:
  Consistent use of the type alias ('Prettier') for PrettierMock improves readability.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

• Draft comment:
  The order of entries in the 'files' array has been changed. Confirm that this reordering is intentional and does not affect package consumers.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

• Draft comment:
  There appears to be a potential typographical error in the maintainer's name on line 11: "JounQin admin@1stg.me (https://www.1stG.me)". Please confirm if the name is spelled correctly or if it should be adjusted.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

• Draft comment:
  Simplified comment note; ensure removal of the '.ts' note does not affect downstream docs.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

• Draft comment:
  Removal of the comment block is acceptable; verify the jest.requireActual typing remains correct.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

• Draft comment:
  Changed file glob pattern to only '*.ts' in mocks; ensure JS mocks are not needed.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

• Draft comment:
  Namespace interface export correctly exposes a callable function with attached properties; verify this pattern meets consumer expectations.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

• Draft comment:
  Using a type alias for 'Fs' and similar patterns appears consistent; no changes required.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

• Draft comment:
  Reordering in the 'files' array is non-functional but ensure packaging behavior remains as expected.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

• Draft comment:
  The detailed comment was shortened (removed reference to using '.ts'). Ensure that the rationale for not using .ts (due to test fixture requirements) is documented elsewhere if needed.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

• Draft comment:
  The block comment was removed from the top. Confirm that any important context regarding file extension restrictions is preserved in documentation if still relevant.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

• Draft comment:
  The 'files' pattern was changed from '/*.{js,ts}' to '/*.ts'. Verify that this change does not exclude any necessary JavaScript mocks.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 40% <= threshold 50%
  The comment is asking the author to verify that the change does not exclude necessary JavaScript mocks. This is a request for confirmation, which violates the rules. However, it does point out a specific change in the file pattern that could potentially lead to issues if not intentional. The comment could be rephrased to suggest checking for missing JavaScript mocks without asking for verification.

• Draft comment:
  The namespace export now extends the function type (format) with additional properties, modeling the default export as a callable function. Ensure that this structure aligns with intended API usage and resolves the export regression.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
  The comment is asking the PR author to ensure that the structure aligns with intended API usage and resolves the export regression. This falls under asking the author to confirm their intention or ensure behavior, which is against the rules.

• Draft comment:
  Refactoring the type extensions (using type aliases for Fs and Prettier) improves clarity. Confirm that these changes don’t impact type compatibility in consuming code.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
  This comment is asking the PR author to confirm that the refactoring doesn't impact type compatibility, which is against the rules. It doesn't provide a specific suggestion or point out a specific issue with the code.

• Draft comment:
  The reordering of the 'files' array does not affect functionality, but double-check that all intended build artifacts are correctly included/excluded.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
  This comment is asking the PR author to double-check something, which is against the rules. It doesn't provide a specific suggestion or point out a potential issue with the code itself.

• Draft comment:
  The maintainer name 'JounQin' appears with an unusual capitalization. Please verify if this is the intended spelling or if it should be adjusted for consistency.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.