feat!: block access to /lib

[ephys]

Pull Request Checklist

• Have you added new tests to prevent regressions?
• Does yarn test or yarn test-DIALECT pass with this change (including linting)?
• Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?
• Did you update the typescript typings accordingly (if applicable)?
• Does the description below contain a link to an existing issue (Closes #[issue]) or a description of the issue you are solving?
• Did you follow the commit message conventions explained in CONTRIBUTING.md?

Description Of Change

This PR prevents users from importing anything other than @sequelize/core and @sequelize/core/package.json.

With this change, it is safe to rework our internal source code without risking to introduce a breaking change.

If users need to access our internals, they should open a feature request so we can expose a properly tested solution.

Breaking change documented: sequelize/website#78

As a last resort, if a user really needs to access them, I added @sequelize/core/_non-semver-use-at-your-own-risk_ as an alias for @sequelize/core/lib. Hopefully it is clear enough that these imports should only be used as a last resort and are not officially supported, and could break in any release, including patch releases.

[WikiRik]

Why would a user want to import our package.json?

[ephys]

Typically to access our version number (even though it's exposed as Sequelize.vesrion), like in this issue #13787. Other packages also expose their package.json even though their other modules are restricted, so there may be reasons I don't know about

[WikiRik]

Can't hurt to export package.json then, so should be good

[github-actions]

🎉 This PR is included in version 7.0.0-alpha.11 🎉

The release is available on:

• npm package (@release-v7 dist-tag)
• GitHub release

Your semantic-release bot 📦🚀