chore: initialize monorepo setup #612
Conversation
Co-authored-by: Nicholas C. Zakas <[email protected]>
There was a problem hiding this comment.
LGTM. Would like @mdjermanovic and @fasttime to review before merging.
|
I'm planning on reviewing this tomorrow. |
README.md
Outdated
| ## Security Policy | ||
|
|
||
| We work hard to ensure that Espree is safe for everyone and that security issues are addressed quickly and responsibly. Read the full [security policy](https://github.com/eslint/.github/blob/master/SECURITY.md). |
There was a problem hiding this comment.
The security policy section is required to comply with one of Tidelift's recommendations. See https://tidelift.com/lifter/package/npm/espree/tasks/packages_have_security_policies.
We could change the link in Tidelift so it points to packages/espree/docs/README.md instead, but I think it would be better to keep it pointing to a page that's not inside a package. Opinions?
There was a problem hiding this comment.
We should probably have it in both places: one that is Espree-specific in the Espree package and one at the repo root that is more generic.
There was a problem hiding this comment.
We should probably have it in both places: one that is Espree-specific in the Espree package and one at the repo root that is more generic.
Sounds good. We could re-add the security policy to the main README.md file but replace "Espree" with something more generic (e.g. "packages in this repository"). I think that's the only change needed.
There was a problem hiding this comment.
Updated root Readme 👍🏻
|
Note: I'm going to update the GitHub repo description after merging, so it's no longer Espree-specific.
|
Refers #609
Changes
packages/espreerelease-pleaseconfiguration to be a monorepo setup (like `eslint/rewrite)Additional information
packages/espree. I'll create separate PRs to move rest of the packages to this repo. There are already too many files changed that the GitHub UI lags when going through file changes. Or do we want to move all the packages in one PR?