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

Remove jsnext main #713

Merged
merged 1 commit into from Dec 7, 2020
Merged

Remove jsnext main #713

merged 1 commit into from Dec 7, 2020

Conversation

bidoubiwa
Copy link
Contributor

jsnext:main is deprecated: rollup/plugins#81 (comment)
Only rollup used to use it but rollup just decided to remove it as well: rollup/plugins#85

Should be merged after: #709

Copy link
Member

@curquiza curquiza left a comment

Choose a reason for hiding this comment

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

bors merge

@bors
Copy link
Contributor

bors bot commented Dec 7, 2020

@bors bors bot merged commit 04e0a1d into master Dec 7, 2020
@bors bors bot deleted the remove-jsnext-main branch December 7, 2020 19:02
bors bot added a commit that referenced this pull request Dec 8, 2020
714: Move jest timeout outside test r=bidoubiwa a=bidoubiwa

Because #713 also timeoud like usual I dig into the same problem again. 
I think maybe it is due to the fact that it is not the `tests` that timeout but the whole jest setup. 
So I tried following this stack overflow: 
https://stackoverflow.com/questions/49603939/message-async-callback-was-not-invoked-within-the-5000-ms-timeout-specified-by

who suggests the following: 
> But this would be specific to the test. Or you can set up the configuration file for the framework.
>
>Configuring Jest
>
>// jest.config.js
>module.exports = {
>  // setupTestFrameworkScriptFile has been deprecated in
>  // favor of setupFilesAfterEnv in jest 24
>  setupFilesAfterEnv: ['./jest.setup.js']
>}
>
>// jest.setup.js
>jest.setTimeout(30000)


Co-authored-by: Charlotte Vermandel <charlottevermandel@gmail.com>
@curquiza curquiza added the skip-changelog The PR will not appear in the release changelogs label Dec 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
skip-changelog The PR will not appear in the release changelogs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants