chore: Remove the src directory from packages.json's files

[sy-records]

Summary

close #1343

What kind of change does this PR introduce? (check at least one)

• Bugfix
• Feature
• Code style update
• Refactor
• Docs
• Build-related changes
• Repo settings
• Other, please describe:

If changing the UI of default theme, please provide the before/after screenshot:

Does this PR introduce a breaking change? (check one)

• Yes
• No

If yes, please describe the impact and migration path for existing applications:

The PR fulfills these requirements:

• When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)

You have tested in the following browsers: (Providing a detailed version will be better.)

• Chrome
• Firefox
• Safari
• Edge
• IE

If adding a new feature, the PR's description includes:

• A convincing reason for adding this feature
• Related documents have been updated
• Related tests have been updated

To avoid wasting your time, it's best to open a feature request issue first and wait for approval before working on it.

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/docsify-core/docsify-preview/3g7nmuq1y
✅ Preview: https://docsify-preview-git-fork-sy-records-remove-src.docsify-core.vercel.app

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit f40c1c4:

Sandbox	Source
docsify-template	Configuration

[trusktr]

This is a breaking change. We should not remove src. Someone may depend on it. Why did you remove it?

[trusktr]

@QingWei-Li Hello! We've been trying to save breaking changes for v5, but first we're stabilizing the code with tests (see Playwright PR, and some new files like docsify.test.js).

In my opinion, src files should always be published. This allows people to integrate source files into their own build systems which may be preferable over consuming built files (something I do quite often).

[anikethsaha]

@trusktr IMO, I don't think we should publish that. is someone who wants to use the source file, they can very well pull it from the Github and also publishing the src folders will increase the package size unnecessary.

This is not a breaking change cause we never recommended nor stated anywhere in the docs to use these files and even if we did so, we should fix that.