You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 14, 2018. It is now read-only.
The current implementation forces all valid truffle boxes to have the truffle project be in the base directory for the repo by checking for a /master/truffle.js.
I am the author of a Truffle Box (link) and I wanted to convert my Truffle Box into a monorepo instead. By that I mean I wanted to separate the frontend client and truffle project into two separate folders (not nested): /truffle and /client.
In other words, I wanted to be able to run truffle unbox <my truffle box name> and immediately get a monorepo of a truffle project and my frontend client in separate folders. However, the current implementation does not allow that and I understand why that might be the case. I assume you want all truffle boxes to deposit the truffle project in the current directory.
Nevertheless, I thought this was worth an issue anyhow.
The text was updated successfully, but these errors were encountered:
The current implementation forces all valid truffle boxes to have the truffle project be in the base directory for the repo by checking for a
/master/truffle.js
.Source
I am the author of a Truffle Box (link) and I wanted to convert my Truffle Box into a monorepo instead. By that I mean I wanted to separate the frontend client and truffle project into two separate folders (not nested):
/truffle
and/client
.In other words, I wanted to be able to run
truffle unbox <my truffle box name>
and immediately get a monorepo of a truffle project and my frontend client in separate folders. However, the current implementation does not allow that and I understand why that might be the case. I assume you want all truffle boxes to deposit the truffle project in the current directory.Nevertheless, I thought this was worth an issue anyhow.
The text was updated successfully, but these errors were encountered: