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

chore: convert jest-cli and jest-validate to esm #8874

Merged
merged 5 commits into from Aug 26, 2019

Conversation

SimenB
Copy link
Member

@SimenB SimenB commented Aug 24, 2019

Summary

We wanna migrate off of export = as it's not valid JS. These ones should be free as they already export objects. Marking them as breaking, but it should just be breaking for people using TS - either import or require should work the same

Test plan

Green CI

@codecov-io
Copy link

codecov-io commented Aug 24, 2019

Codecov Report

Merging #8874 into master will not change coverage.
The diff coverage is 0%.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #8874   +/-   ##
=======================================
  Coverage   64.12%   64.12%           
=======================================
  Files         275      275           
  Lines       11629    11629           
  Branches     2845     2846    +1     
=======================================
  Hits         7457     7457           
  Misses       3545     3545           
  Partials      627      627
Impacted Files Coverage Δ
packages/babel-plugin-jest-hoist/src/index.ts 0% <ø> (ø) ⬆️
packages/jest-jasmine2/src/index.ts 0% <0%> (ø) ⬆️
packages/jest-jasmine2/src/jasmine/jasmineLight.ts 0% <0%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6e6a8e8...a238374. Read the comment docs.

packages/jest-cli/src/index.ts Outdated Show resolved Hide resolved
@@ -5,6 +5,12 @@
* LICENSE file in the root directory of this source tree.
*/

import * as cli from 'jest-cli';
export {
Copy link
Member Author

Choose a reason for hiding this comment

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

followup from last question, should we ditch these exports as well?

A reason not to is that we don't really have a programmatic API yet (and won't from jest 25), so all we'd do is ask people to import directly from @jest/core or jest-cli. I think that if we first ask people to change their imports, we should also give them a real API rather than the internal ones that are used now

Copy link
Collaborator

Choose a reason for hiding this comment

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

As long as we don't have clear vision of the new API, I wouldn't change that just yet

@github-actions
Copy link

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 11, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants