-
Notifications
You must be signed in to change notification settings - Fork 859
docs: clarify yarn install purpose in README #4629
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
base: main
Are you sure you want to change the base?
docs: clarify yarn install purpose in README #4629
Conversation
|
DCO Assistant Lite bot All contributors have signed the DCO. |
|
@carbon-design-system maintainers — I'd love your feedback on this small improvement to the README. I'm a first-time contributor. 🙂 |
Signed-off-by: Subham Sangwan <[email protected]>
470aa00 to
2cb6c6a
Compare
|
Hi 👋, first-time contributor here! I’ve signed off the commit to fix the DCO error. Kindly requesting workflow approval and a review when convenient. Thank you! 🙌 |
|
I have read the DCO document and I hereby sign the DCO. |
…ADME Signed-off-by: Subham Sangwan <[email protected]>
8ed5d76 to
0e3346b
Compare
|
Hi team 👋 — all checks are now passing including the DCO. The Netlify preview is still blocked due to needing workflow approval from a maintainer. As this is a small docs change and I’m a first-time contributor, I’d really appreciate a quick review and workflow approval when you get a chance. Thank you! 😊 |
|
Hi @emyarod @annawen1 @alina-jacob — |
|
Hi again 👋 Just a gentle follow-up on this PR. All checks are now passing ✅ Happy to make any changes if needed — thanks again for your time! 🙌 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @Subham-KRLX, thanks for taking the time to contribute! Is there a specific issue that was opened for the changes you're making in this PR? Some of the changes like adding the develop script or the yarn install description seem a bit redundant / unnecessary to me.
|
Hi @annawen1, thanks for your feedback! |
|
Hi @annawen1 👋 I've updated the README based on your feedback — the install clarification is retained, and the extra parts have been trimmed as discussed. |
|
@tay1orjones Thanks for the thorough review! I'll:
Will push these updates shortly. Appreciate your guidance on maintaining project standards! |
- Improved README formatting and clarity - Removed Sass config from gatsby-config.js - Cleaned package.json (removed redundant scripts and Sass deps) - Fixed version number formatting
|
@tay1orjones |
|
hey,@alisonjoseph All DCO checks pass. Let me know how to fix. |
fcf738a to
df01bd7
Compare
tay1orjones
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm still seeing gatsby-plugin-sass, path-browserify, and sass listed as hard deps. Removing those and running yarn install will update the yarn.lock.
Deploy previews only run for maintainers with write access to the repo for security reasons, but we can test changes locally still.
| // Explicitly resolve @carbon packages to their node_modules path | ||
| '@carbon/react': path.resolve(__dirname, 'node_modules/@carbon/react'), | ||
| '@carbon/icons-react': path.resolve(__dirname, 'node_modules/@carbon/icons-react'), | ||
| '@carbon/styles': path.resolve(__dirname, 'node_modules/@carbon/styles'), // Keep for Sass if needed | ||
| }, | ||
| // Fallback for older module resolution patterns | ||
| fallback: { | ||
| 'crypto': false, // Example of adding fallbacks if needed for older modules | ||
| 'stream': false, | ||
| 'path': require.resolve('path-browserify'), // Ensure path resolves correctly | ||
| // You might need more if other 'cannot resolve' errors appear for node built-ins | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is this for?
| }, | ||
| }); | ||
|
|
||
| // Disable sourcemaps in production |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
imo this is valuable as devtool: false doesn't really convey relation to sourcemaps
| ``` | ||
| yarn build | ||
| ``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why remove code formatting for this?
|
|
||
| ``` | ||
| src | ||
| ├── components |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
removing the backtics cause this to not be formatted properly. I'd just leave them in.
|
Also if you run |
Closes #
Improves README documentation clarity for first-time contributors
Changelog
Changed
yarn installpurpose in README to explicitly mention it installs dependencies frompackage.jsonRemoved
developscript from package.json (duplicate ofdev)