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 dependencies and fix import. #16

Merged
merged 15 commits into from
Mar 15, 2024
Merged

Update dependencies and fix import. #16

merged 15 commits into from
Mar 15, 2024

Conversation

davidlehn
Copy link
Member

No description provided.

Copy link
Member

@dlongley dlongley left a comment

Choose a reason for hiding this comment

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

LGTM, AFAICT. Thanks!

@davidlehn
Copy link
Member Author

LGTM, AFAICT. Thanks!

It may have looked good... it was not. It didn't work in top-level apps that use bedrock-webpack due to a UMD bundle override. Removed that and webpack will now use ESM bundle in ESM apps. I don't think there is an issue with doing this in general these days. However, that override caused any quasar usage to use UMD, and those bundles have some differences. Changing to ESM bundle can break apps, depending on their usage, so it's a major change. I put in patches for a few other packages, and others can be updated as needed.

Copy link
Member

@dlongley dlongley left a comment

Choose a reason for hiding this comment

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

Bummer it had to be breaking, but it's for the best. Thanks!

- Test with Node.js 20.x.
- Update action verions.
- Update all dependencies.
- Update quasar import to avoid errors due to no default export.
**BREAKING**: Remove `animate.css` `compat` override and use latest
style.  See the [migration guide](https://animate.style/#migration) for
details on updating.
Using ESM vs UMD for Quasar means plugins are no longer used
automatically or by default. Applications must be initialized with
Quasar plugins it uses. This is currently not automatic and requires
top-level application knowledge of all sub-modules in use and what
plugins they require. The `quasarOptions` object added here can be used
for this purpose and for other Quasar options.
Copy link
Contributor

@mattcollier mattcollier left a comment

Choose a reason for hiding this comment

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

TY

CHANGELOG.md Show resolved Hide resolved
package.json Show resolved Hide resolved
@mattcollier
Copy link
Contributor

@davidlehn We're running into issues with Quasar 2.14.6 in multiple projects now. Can you keep moving this forward to a release? Thank you.

@davidlehn davidlehn merged commit 258e837 into main Mar 15, 2024
1 check passed
@davidlehn davidlehn deleted the update-dependencies branch March 15, 2024 01:02
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.

3 participants