Skip to content

Conversation

@PVince81
Copy link
Member

Adjust webpack config to accomodate for the updates of @babel/preset-env from #899

Fixes nextcloud/server#26314

Inspired by a similar issue we had on the talk repo: nextcloud/spreed@5673db9#diff-3e31f6f375484b2dfd4629faed9e5183ac6568ebdbc67ec752e10c41a35250c6R72

@PVince81
Copy link
Member Author

/compile amend /

Adjust webpack config to accomodate for the updates or @babel/preset-env

Signed-off-by: Vincent Petry <vincent@nextcloud.com>
Signed-off-by: npmbuildbot-nextcloud[bot] <npmbuildbot-nextcloud[bot]@users.noreply.github.com>
@npmbuildbot-nextcloud npmbuildbot-nextcloud bot force-pushed the bugfix/noid/fix-babel-loading-exports-not-defined branch from 5149738 to 7552bbc Compare March 26, 2021 10:21
@nickvergessen nickvergessen requested a review from skjnldsv March 26, 2021 10:22
Copy link
Member

@MorrisJobke MorrisJobke left a comment

Choose a reason for hiding this comment

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

🐘

@nickvergessen
Copy link
Member

Seems to work and we do the same in talk, but I'd still like confirmation by another JS expert

@PVince81
Copy link
Member Author

/compile amend /

@npmbuildbot-nextcloud npmbuildbot-nextcloud bot force-pushed the bugfix/noid/fix-babel-loading-exports-not-defined branch from 01426a5 to b86c718 Compare March 26, 2021 11:17
@PVince81
Copy link
Member Author

CI is green. I've also retested this PR's state after checking it out again and it works.

@skjnldsv are you ok with the babelrc changes ?

@nickvergessen
Copy link
Member

Merge with babel.config.js please

@PVince81 PVince81 force-pushed the bugfix/noid/fix-babel-loading-exports-not-defined branch from b86c718 to 5c183ac Compare March 26, 2021 11:46
Copy link
Member

@nickvergessen nickvergessen left a comment

Choose a reason for hiding this comment

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

see above

@PVince81
Copy link
Member Author

done. merged the configs, tested then squashed

@PVince81
Copy link
Member Author

I did run make dev-setup && make build-js-production every time, and yet it doesn't accept my compiled assets.

@PVince81
Copy link
Member Author

/compile amend /

Signed-off-by: Vincent Petry <vincent@nextcloud.com>
Signed-off-by: npmbuildbot-nextcloud[bot] <npmbuildbot-nextcloud[bot]@users.noreply.github.com>
@npmbuildbot-nextcloud npmbuildbot-nextcloud bot force-pushed the bugfix/noid/fix-babel-loading-exports-not-defined branch from 5c183ac to ac70fa9 Compare March 26, 2021 11:49
@skjnldsv
Copy link
Member

I wonder if we could have a global babel config too.
Would be nice

@PVince81
Copy link
Member Author

I wonder if we could have a global babel config too.
Would be nice

I wonder too, but won't be delivered today.
There's a master branch that is waiting to be unblocked: nextcloud/server#26314

@skjnldsv skjnldsv merged commit 330f50a into master Mar 26, 2021
@skjnldsv skjnldsv deleted the bugfix/noid/fix-babel-loading-exports-not-defined branch March 26, 2021 11:59
@skjnldsv
Copy link
Member

I wonder too, but won't be delivered today.

Let me test

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[master] Consistent sharing acceptance test failure

5 participants