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 and fix babel building #2471

Merged
merged 4 commits into from Nov 19, 2019
Merged

Conversation

magicznyleszek
Copy link
Member

Description

New babel isn't so forgiving in exports, so it needed quite a few changes.

Related issues

Fixes #2012

@magicznyleszek magicznyleszek changed the title update exports Update and fix babel building Oct 23, 2019
@noliveleger noliveleger requested review from noliveleger and removed request for jnm November 19, 2019 15:24
@noliveleger noliveleger assigned noliveleger and unassigned jnm Nov 19, 2019
Resolved Conflicts:
	jsapp/js/components/RESTServices/RESTServicesForm.es6
	jsapp/js/components/permissions/userAssetPermsEditor.es6
	jsapp/js/components/textBox.es6
	package-lock.json
Copy link
Contributor

@noliveleger noliveleger left a comment

Choose a reason for hiding this comment

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

LGTM 👍

@magicznyleszek, For my information (and my curiosity), why sometimes you choose a named export over a default export?
e.g. import {keymap} from './keymap';
I would have thought keymap should be a default export.

@noliveleger noliveleger merged commit a7d9feb into two-databases Nov 19, 2019
@noliveleger noliveleger deleted the 2012-update-babel-2db branch November 19, 2019 19:21
@magicznyleszek
Copy link
Member Author

@noliveleger I don't have an opinion on this, I just do what works :-P (:-1: me). After updating one of the dependencies build process started to complain about unnamed default exports, so I changed them. But then some other dependency also got updated and I think it doesn't complain anymore, as I was able to change keymap to unnamed default export 🤷‍♀ I read about some reasoning as to why it is potentially dangerous to use unnamed default exports, but don't remember what it was exactly - something about overwriting variables…

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.

None yet

3 participants