v4.0.0-beta

[danielpza]

v4.0.0-beta

See #427

compare changes

💅 Refactors

• ⚠️ Esm only (#442)

📖 Documentation

• Update readme (a979660)
• Add maintenance section to the readme (7bd130f)
• Add reproduction example (d265d0b)
• Add issue templates (#443)
• Add v4 migration draft (877c489)

🏡 Chore

• Fix readme formatting (c31284b)
• ⚠️ Remove main and types package.json properties (ec9ae9c)
• ⚠️ Remove typescript 3 support (3de3d81)
• ⚠️ Remove typescript 4.7 support (e372543)
• ⚠️ Require node >= 22 (d475adf)
• ci: Update node version testing matrix (30c8729)
• Remove nx plugin (6fbdadc)
• ⚠️ Remove ts-node register interface (58a0db0)
• Revert "chore: remove nx plugin" (7948a8e)
• deps-dev: Bump typescript from 5.7.2 to 5.9.3 in /test (e564526)

✅ Tests

• Replace jest with node test runner (c77edec)

⚠️ Breaking Changes

• ⚠️ Esm only (#442)
• ⚠️ Remove main and types package.json properties (ec9ae9c)
• ⚠️ Remove typescript 3 support (3de3d81)
• ⚠️ Remove typescript 4.7 support (e372543)
• ⚠️ Require node >= 22 (d475adf)
• ⚠️ Remove ts-node register interface (58a0db0)

❤️ Contributors

• Daniel Perez (@danielpza)

---

This discussion was created from the release v4.0.0-beta.

[lppedd]

Quick feedback:

• Could you add ^4.0.0 compatibility details to the table at the bottom of the README?
• Since it appears you're now requiring TS >=5.8.x, does it make sense to refine the peerDependencies range to ^5.8.0? Currently it's just >=5.

[danielpza]

Could you add ^4.0.0 compatibility details to the table at the bottom of the README?

👍 LGTM Feel free to send a PR

Since it appears you're now requiring TS >=5.8.x, does it make sense to refine the peerDependencies range to ^5.8.0? Currently it's just >=5.

Technically we didn't change the code logic so it should still work with the ^5.x.x range.
I updated the dependency to make sure it works in the latest (at the time) version of typescript and shouldn't affect olders v5 typescript versions

[danielpza]

I published v3.5.6 which should make it a bit easier to migrate to v4 by backporting the typescript-transform-paths/plugins/nx export.

The new export typescript-transform-paths/plugins/nx is available in v3.5.6:

   "transformers": [
     {
-      "name": "typescript-transform-paths/nx-transformer",
+      "name": "typescript-transform-paths/plugins/nx",
       "options": { "afterDeclarations": true },
     },
   ],

This is a small change but hopefully eases the upgrade

cc @lppedd

[danielpza]

@lppedd thanks for the feedback, that's good to hear.

I haven't heard of any other issues so far. I'll publish the v4 version and make it the default version

[lppedd]

@danielpza hey! What do you think about releasing a 4.0.0? I haven't encountered a single issue in the last beta.
Would also be nice to state what the compatibility with TS 6.0.0+ is.

[danielpza]

Hey, sorry for the late reply, it's been busy these weeks.

Would also be nice to state what the compatibility with TS 6.0.0+ is.

personally I haven't tried it myself. If you or anyone else want to try it with TS 6 and send a PR with the compatibility details I'll gladly merge it.

What do you think about releasing a 4.0.0? I haven't encountered a single issue in the last beta.

I've been dragging my feet since I the npm tokens on GH have expired and I need to generate new ones ... or do it manually. I'll try to get back to this soon.

[danielpza]

Hey @lppedd, I just published version 4.0.0!
Thanks for testing the beta and making sure it was good.

[lppedd]

@danielpza thank you! I did some preliminary testing (with the latest Beta) with Nx 23.x and TS 6.0.3 and it seems to work. I need to do deeper analysis of the output tho.