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
When this was removed c22e5f6#diff-e06054b3fcc75704ac7a1aaa88d7f7d465a7ea5f659c2b386e8d3483f8f1a779L61
It broke how config files are found: https://github.com/milesj/boost/blob/master/packages/config/src/helpers/createFileName.ts#L19
And packages can only use packemon.config.js naming style now.
Not a bug since the fix is to just rename the config files, but probably needs docs updating
The text was updated successfully, but these errors were encountered:
@wespickett It's still supported, it's just that the "root" is the cwd. So if you're running the command in a sub-folder, and that's the cwd, then it doesn't traverse upwards. It's all based on this: https://packemon.dev/docs/migrate/3.0#no-longer-workspaces-aware-by-default
Sorry, something went wrong.
Try adding DEBUG=* and see what it spits out.
DEBUG=*
No branches or pull requests
When this was removed
c22e5f6#diff-e06054b3fcc75704ac7a1aaa88d7f7d465a7ea5f659c2b386e8d3483f8f1a779L61
It broke how config files are found:
https://github.com/milesj/boost/blob/master/packages/config/src/helpers/createFileName.ts#L19
And packages can only use packemon.config.js naming style now.
Not a bug since the fix is to just rename the config files, but probably needs docs updating
The text was updated successfully, but these errors were encountered: