fix: resolve #206 — change index.js point to './src/core' break test cases follow README

[ed-thuando]

Summary

fix: resolve #206 — change index.js point to './src/core' break test cases follow README

Problem

Severity: Medium | File: index.js

The main entry point (index.js) changed to simply re-export from './src/core'. This breaks backwards compatibility for users who were importing from the main package entry point (e.g., require('jscodeshift')).

Solution

Combined multi-file contribution:

• Docs: index.js re-exports from './src/core'
• Docs: Core module exports
• Docs: testUtils is not re-exported from core
• Docs: Check what core.js exports and includes

Files changed: index.js, src/core.js

Changes

• index.js (modified)
• src/core.js (modified)

Testing

• Existing tests pass
• Manual review completed
• No new warnings/errors introduced

---

Generated by ContribAI v6.0.0

[vercel]

@ed-thuando is attempting to deploy a commit to the Meta Open Source Team on Vercel.

A member of the Team first needs to authorize it.

[changeset-bot]

⚠️ No Changeset found

Latest commit: c16541a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[meta-cla]

Hi @ed-thuando!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!