We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hello,
I'm trying to deploy with now (v.2) a monorepo project which uses svgo, and svgo is using a default config file from node_modules/svgo/.svgo.yml.
now
svgo
node_modules/svgo/.svgo.yml
♻️ During the build phase, on step [5/5] when now is cleaning modules the .svgo.yml file is removed.
.svgo.yml
I tried to add a .yarnclean file with !.svgo.yml inside but no success.
.yarnclean
!.svgo.yml
Any ideas how can I prevent the cleanup step or fix this?
Error: ENOENT: no such file or directory, open '//../../.svgo.yml'
The svgo issue.
The text was updated successfully, but these errors were encountered:
Im having a similar issue when using shopify-api-node, some folders get wiped from the module during build.
Sorry, something went wrong.
This is most likely an issue with node-file-trace, so I will transfer this issue over there.
node-file-trace
I am unable to reproduce the issue with the latest node-file-trace and latest svgo.
npm i -g @zeit/node-file-trace mkdir example && cd example yarn add svgo echo "const svgo = require('svgo')" > index.js nft print index.js | grep yml # prints "node_modules/svgo/.svgo.yml"
This prints the expected node_modules/svgo/.svgo.yml.
No branches or pull requests
Hello,
I'm trying to deploy with
now
(v.2) a monorepo project which uses svgo, andsvgo
is using a default config file fromnode_modules/svgo/.svgo.yml
.♻️ During the build phase, on step [5/5] when
now
is cleaning modules the.svgo.yml
file is removed.I tried to add a
.yarnclean
file with!.svgo.yml
inside but no success.Any ideas how can I prevent the cleanup step or fix this?
The
svgo
issue.The text was updated successfully, but these errors were encountered: