fix: support type: module with .cjs file extension #2342

[alexanderniebuhr]

close #2342

TODO:

• Update CHANGELOG.md* with your change (include reference to issue & this PR)
• Make sure all of the significant new logic is covered by tests
• Rebase your changes on master so that they can be merged easily
• Make sure all tests and linter rules pass

*Make sure changelog entries note which project(s) has been affected. See older entries for examples on what this looks like.

[apollo-cla]

@alexanderniebuhr: Thank you for submitting a pull request! Before we can merge it, you'll need to sign the Apollo Contributor License Agreement here: https://contribute.apollographql.com/

[alexanderniebuhr]

Not sure why CI Tests fail. Local Tests are passing all

[alexanderniebuhr]

@jgzuke just saw you answering PRs and doing heavy work on the transition branch.
If you move the apollo vs code extension, it would be great to get this included asap.

Let me know if you need any more information!

[alexanderniebuhr]

apollographql/vscode-graphql#4

[abernix]

@alexanderniebuhr Thanks for moving that over to the new VS Code repository. Since there are remaining bits in this repository (e.g., the apollo CLI) that also use this file (it's a platform concern), should we re-open this and land this PR?

[abernix]

Conflicts look like they need to be resolved locally and I believe that all the CI failures are from linting (e.g., a run of prettier via npm run lint-fix)

apollo-tooling/package.json

Line 27 in c05c9e4

"lint-fix": "prettier --write \"packages/*/src/**/*.{js,jsx,ts,tsx}\"",

[alexanderniebuhr]

@abernix yeah you could reopen this and land it. My main concern was the VS Code Extension, so I just moved it over to the new repo.
I can solve conflicts and run prettier for you