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
npm init -f
allow users to include a package.json instead of just using npm init -f
Users can add a package.json file:
.r2g/package.json
which will be the package.json file of Y, the testbed project.
In that package.json file, they can include test dependencies if they want.
This might not be a good idea, because it may conflate deps that won't actually exist IRL.
The text was updated successfully, but these errors were encountered:
this is almost certainly a bad idea
Sorry, something went wrong.
No branches or pull requests
allow users to include a package.json instead of just using
npm init -f
Users can add a package.json file:
.r2g/package.json
which will be the package.json file of Y, the testbed project.
In that package.json file, they can include test dependencies if they want.
This might not be a good idea, because it may conflate deps that won't actually exist IRL.
The text was updated successfully, but these errors were encountered: