-
Notifications
You must be signed in to change notification settings - Fork 13
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
DEV: add pnpm compat in preparation of new changes to theme-skeleton #48
Conversation
595606a
to
75c983a
Compare
@@ -0,0 +1,12 @@ | |||
{ |
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.
adding this file is necessary for tests to pass - yarn simply creates empty node_modules and lockfile, but pnpm install would raise an error here. In any case, we should expect the actual theme skeleton repo to always have at least a package.json file.
@@ -36,7 +36,7 @@ Gem::Specification.new do |spec| | |||
spec.add_development_dependency "guard" | |||
spec.add_development_dependency "guard-minitest" | |||
spec.add_development_dependency "webmock" | |||
spec.add_development_dependency "rubocop-discourse", "~> 3.6.0" | |||
spec.add_development_dependency "rubocop-discourse", "~> 3.8.1" |
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.
Update required to resolve an earlier error raised in linting CI step.
Co-authored-by: Jarek Radosz <[email protected]>
We are preparing to switch to
pnpm
for all themes/plugins now that the change has landed in core. This change makes the discourse_theme CLI compatible with that change to theme-skeleton. We will remove all usage of yarn in an upcoming minor version bump once pnpm is fully rolled out.For more context: https://meta.discourse.org/t/discourse-core-is-switching-to-pnpm-for-js-package-management/324521