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

update plugin for mirador 4 #301

Open
wants to merge 7 commits into
base: main
Choose a base branch
from
Open

update plugin for mirador 4 #301

wants to merge 7 commits into from

Conversation

fstoe
Copy link

@fstoe fstoe commented Aug 1, 2024

Hello,
these changes prepare the plugin for the Mirador4/Mui5/React 18 upgrade.

  • i ran mui codemods, integrated styled components
  • fixed the tests
  • updated the dependencies
  • added webpack
  • updated prettier/eslint/babel

Copy link
Member

@jbaiter jbaiter left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks a lot for the PR ❤️ !

Besides the line-by-line comments, some general notes:

  • Please do the formatting in a separate commit next time, makes reviewing a lot easier :-)
  • The .tgz file probably shouldn't be checked into git

},
},
],
].filter(Boolean),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is that neccessary here? All the plugin definitions are truthy, non?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some of the plugins are used in different env modes. So they can be faulty.

package.json Outdated
"lint": "eslint ./src ./__tests__",
"format": "eslint --fix ./src ./__tests__",
"prepublishOnly": "npm run build",
"start": "nwb serve-react-demo",
"parcel": "parcel demo/src/index.html",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

parcel is not listed as a dev dependency, so this can probably be removed?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh thanks. I just removed it :)

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

Successfully merging this pull request may close these issues.

2 participants