Skip to content
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

.packemon.js config file naming no longer supported #201

Open
wespickett opened this issue May 12, 2023 · 2 comments
Open

.packemon.js config file naming no longer supported #201

wespickett opened this issue May 12, 2023 · 2 comments

Comments

@wespickett
Copy link
Contributor

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

@milesj
Copy link
Owner

milesj commented May 13, 2023

@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

@milesj
Copy link
Owner

milesj commented May 13, 2023

Try adding DEBUG=* and see what it spits out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants