kulshekhar / ts-jest

A Jest transformer with source map support that lets you use Jest to test projects written in TypeScript.

Home Page:https://kulshekhar.github.io/ts-jest

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Looking for collaborators

kulshekhar opened this issue · comments

I'm looking for collaborators to help take ts-jest forward. If you want to become a collaborator, please leave a comment below.

Collaborator responsibilities include:

  • Improving documentation
  • Responding to issues
  • Reviewing and merging pull requests
  • Development contributions: improving code quality, adding features, fixing bugs
  • Establish and manage a release process

You can be as much or as little involved as you want.

I might be interested in lending a hand - you're doing good work here :)

I'd like to contribute 1-2 hours a week, more when I can. I won't be able to actively contribute until 6/2 though.

Doing great work here. I hope you get dozens of collaborators. This package makes testing TypeScript with Jest almost painless.

This package makes testing TypeScript with Jest almost painless.

that's why I'm looking for help here - to remove the 'almost' 😄

commented

Maybe I can put some hours a week into this?

@morajabi that's great!

Do you want to take a stab at one of the open issues?

I would love someone to give a hand with #217

commented

Let me take a look. @GeeWee

commented

One thing, can someone explain to me what are we doing here to make TS+Jest work? Or what are problems with TS and Jest?

In fact, I wasn't into testing things until a few months ago and this would help me a lot to contribute more. Thanks!
@GeeWee @kulshekhar @bcruddy

@morajabi

can someone explain to me what are we doing here to make TS+Jest work?

I initially created ts-jest for one reason - sourcemaps. When I created and used a custom transformer based on Jest's example, I realized that it didn't display the correct line numbers. So, in a nutshell, that was why ts-jest was created.

does that answer your question?

commented

@kulshekhar That made the main reason clear, Thanks!

Can you explain how you solved the problem here? What's the process here and what tool are we using to achieve that?

We inject a small piece of code at the top of every file that we process.

This code makes use of source-map-support to add mapping information to all the files that are being processed.

commented

Aha, and when do we transpile .ts code to JS?

Whenever Jest invokes the process function that ts-jest exports

commented

Great! Thank you @kulshekhar, Now that I know these I can read the source and find out everything.
Can you suggest me some reading about how Jest and processors work? or anything related that'd help me (or any new comers)?

@kulshekhar, if you still needs folks let me know! I can do a few hours a week.

@abmohan welcome aboard!

@kulshekhar still recruiting? Wouldn't mind lending a hand. Seeing alot of any's throughout the codebase. Would replacing those with generics for type inference be a good place to start?

@CarloPalinckx any help is always welcome. Replacing anys with sensible types is as good a place to start as any :)

Would love some PRs that fixed types!

@kulshekhar - just saw your notification, thank you.

Assuming PRs that replaced anys with types are still the best place to start?

@abmohan yeah, that would be a good place to start. If there are any open issues that you'd like to tackle that could be good as well. Basically, anything that improves the package is very welcome :)

I would like to help as well. Namely I would like to see through an upgrade to Babel 7.

@severen any help is welcome :)

@kulshekhar Glad to be one.

I'm going to be a bit out of the loop for the next few weeks. Just had to put my dog down - so if anyone sees anything that's waiting on me that they want to jump on - go ahead.

Im keen to contribute in any way I could. A few hours a week.

@dasmedium any help is very welcome!

I would like to help as well, maybe few hours a week.

are there any list of minimum [tech] knowledge requirements to help with the project?

Not at all - if you think the source code is fairly understandable you should be good to go! I ended up learning a lot about both typescript, babel and a variety of other topics working on this :)

@GeeWee that being the case, I'm interested in contributing to it :)

Welcome aboard! Feel free to grab an issue you can contribute to, Up to date docs is probably what we're lacking the most at the moment! There's a slack channel as well, i think @huafu can tell you more.

Welcome @Fazendaaa!
Yup, the slack channel is very new and free from anybody but contributors for now (until we'll advertise about it), but you can join, I am there and I'll be happy to explain you whatever I do can explain.

Closing this as discussed in slack from this message

I'm a passionate user of ts-jest and am highly interested in helping build it! Count me in

I'm open to help!

Let me know how can I help the project.