Hi Mohammad,

Thanks! I found a couple of issues in the Makefile.PL diff:

1. In provides, some file paths don’t match the actual repo files:

• lib/JQ/Lite/Uti/Parsingl.pm should be lib/JQ/Lite/Util/Parsing.pm
• lib/JQ/Lite/Util/Paths should be lib/JQ/Lite/Util/Paths.pm

2. clean => { ... } looks like it ended up inside the provides block (and the braces don’t appear to close properly).
   clean should be a top-level argument to WriteMakefile, not inside META_MERGE/provides.

Also, could we avoid hard-coding the version in provides to keep it in sync with VERSION_FROM?

If you update the PR accordingly, I’ll merge it.

Best regards,
Shingo

Hi @kawamurashingo,

Thanks for prompt review.

1. I have fixed the typo in path for 'provides'.
2. I have removed hardcode version too, now pulling it on the fly.

With regard to the key 'clean', it seems fine to me and not inside 'provides'.

Best Regards,
Mohammad

Thanks for the PR! This is a very helpful improvement for CPAN metadata, but there is one critical typo that needs to be fixed before merging.

There is a typo in Makefile.PL under the provides section:

'JQ::Lite::Util::Parsing' => { file => 'lib/JQ/Lite/Uti/Parsing.pm' },
                                      ^^^

It should be Util, not Uti:

'JQ::Lite::Util::Parsing' => { file => 'lib/JQ/Lite/Util/Parsing.pm' },

If this is merged as-is, the CPAN META will map the module to a non-existent file, which can break indexing and tooling.

Also, this PR removes META.yml and META.json from MANIFEST.
If the project expects these files to always be included in make dist tarballs, this change may be risky.
(If they are treated as generated artifacts only, then it’s fine, but it should be intentional.)

Suggestion

• Fix Uti → Util (required)
• Then merging is OK
• Reconsider whether META.* should stay in MANIFEST based on release policy

Thanks — once the typo is fixed this PR looks good 👍

@kawamurashingo Point taken well, I have updated the pull request accordingly.