-
Notifications
You must be signed in to change notification settings - Fork 778
feat(react-email, create-email): Use internal implementation for tree function instead of using tree-cli
#1221
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Ignored Deployment
|
2645296
to
9fe0350
Compare
9fe0350
to
8f8c645
Compare
Hey @gabrielmfern, are we just waiting for a review to get this merged? Anything I can do to help? |
@michaelhays Hey, heads up, we just released this under |
Thank you sir! I'll try them out! |
… function instead of using `tree-cli` (#1221)
Following up, 2.1.1 no longer gives me the Snyk warnings 🙏 Thanks again! |
What was the issue?
Some time ago we switched from using
tree-node-cli
to usingtree-cli
astree-node-cli
was causingissues for someone trying to download the CLI behind a corporate proxy.
The new library
tree-cli
though is unmaintained and seems to depend on some librariesthat were being caught by some security measures mentioned here #1153.
This fixes this by having our implementation of the tree functionality
both in
create-email
and inreact-email
which is not very hard to maintainand comes along with tests to verify this works properly.
How can I test to make sure it's fixed?
node src/index.js
inside of./packages/create-email
If you try running the
export
command from the CLI, which is the other place that depends onthis
tree
functionality, you will probably have an error here which #1214 fixes.Closes #1153