chore(deps): update dependency tsdx to ^0.14.0 #61
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^0.13.2
->^0.14.0
Release Notes
formium/tsdx (tsdx)
v0.14.1
Compare Source
Bugfixes
An upstream cache bug that affected certain combinations of build formats has been fixed
The built-in
lodash
->lodash-es
replacement no longer breaks imports oflodash/fp
Dependencies
eslint-config-react-app
has been resolvedCommits
Lists of commits:
Bugfixes
Dependencies
GitHub
Internal
All Contributors
Commit Range
v0.14.0
Compare Source
BREAKING CHANGES
Slightly Breaking Changes
Node 10+
Updated the required Node version from 8 to 10.
While previous versions of TSDX began deprecating support for Node 8, it was not officially dropped.
In this release, we have officially dropped Node 8: TSDX now requires Node 10+ as many dependencies that were upgraded similarly do.
This should not impact most users as Node 8 has been EoL for ~9 months now.
Many packages had already required Node 10+ and the vast majority already have support for it.
Most users are on Node 12 or Node 14 already.
Jest 25
Updated the Jest version used by
tsdx test
from 24 to 25.The main breaking change in Jest 25 is the upgrade of the default JSDOM environment from JSDOM v11 to JSDOM v15.
For most Jest users, this change either has no impact or will reduce configuration if you've manually set a more up-to-date
jest-environment-jsdom
in yourjest.config.js
.In some rare cases, where code relied on the old version of JSDOM, this may result in breakage.
ts-jest
andjest-plugin-typeahead
have also been upgraded to support Jest 25.Babel Changes
babel-plugin-transform-async-to-promises
->babel-plugin-polyfill-regenerator
async-to-promises
has been unmaintained for around a year now and has several correctness issues, many of which have affected TSDX users. For that reason, we've switched to usingbabel-plugin-polyfill-regenerator
instead, which will add a pure, non-pollutingregenerator-runtime
polyfill if yourtargets
require it.The vast majority of browsers (94.37%) now support async/await and generators with no polyfilling necessary, but the default
preset-env
will add it. If you don't already have one, we recommend adding a.browserslistrc
(orpreset-env
targets
) to specify the environments you're targeting.This should be totally backward-compatible, but it may change the output quite a bit, including making bundles larger due to inclusion of
regenerator-runtime
.babel-plugin-macros
TSDX's internal Babel plugin ordering has changed, moving
babel-plugin-macros
to be first.This was done in order to support several use-cases like
styled-components/macro
, which previously did not work due to the ordering.This shouldn't really break anything, but there is an off chance it might have an impact on some rare builds.
Improvements
babel-plugin-polyfill-regenerator
change above, TSDX now supports polyfilling generators out-of-the-box. Previously we only supported async/await withbabel-plugin-transform-async-to-promises
and required users to configure their own plugins for generator polyfillingstyled-components/macro
support per above--max-warnings
flag has been added totsdx lint
, which works the same as ESLint's--max-warnings
flagTemplate Improvements
size-limit
has been added to all templates for bundle analysis via NPM/Yarn scripts and a GitHub Actionbahmutov/npm-install
tsconfig.json
now setskipLibCheck
,forceConsistentCasingInFileNames
, andnoEmit
tsc
for type-checking.skipLibCheck
will also greatly increase performance oftsc
's type-checkingtsconfig.json
now have detailed comments explaining nearly every configuration option in useDocs
patch-package
is now officially listed as a customization optionDependencies
@babel/preset-env
was updated to the latest minor to support nullish coalescing and optional chaining without additional plugins, as well as to update the compatibility table.preset-env
or Autoprefixer, as TSDX's internal test suite does, you may need to update those snapshots.yarn-deduplicate
, overall install size should have decreased a good bitCommits
Lists of commits:
Improvements
--max-warnings
flag totsdx lint
(#858) dd92fecBugfixes
Template Improvements
Docs
patch-package
reference to Customization section (#855) 08a8ef8Dependencies
GitHub
Internal
All Contributors
Commit Range
Postscript
Apologies again for the delay on getting to
v0.14.0
, COVID added a lot of stress and work had been busy, to say the least. Unfortunately I wasn't able to get to all the changes I wanted to into it, but v0.14.0 has been waiting long enough. Only two complex issues were left out and many more PRs added in, though not everything had made it intov0.13.x
either.I also wanted to push Rollup 2, TS 4.0, Prettier 2, and ESLint upgrades into this, but the breaking changes in the changelog started getting too big, so I decided to wait a bit to split those changes across more releases to not throw too much breakage at users at once.
If you're wondering, all of my co-workers, my team, and I were suddenly laid off just over a week ago, so that's why I had time (and want to distract myself) to push out ~2 dozen PRs the past week 😕
Best wishes and stay safe to everyone!
v0.13.3
Compare Source
Optimizations
Template Bugfixes
baseUrl
orpaths
set in theirtsconfig
, fixing a long-standing bugTemplate Docs
Commits
Lists of commits:
Optimizations
Template Improvements
Template Bugfixes
Template Docs
Docs
GitHub
Internal
All Contributors
Commit Range
Postscript
Apologies for the delay on releasing this and the delay on getting to
v0.14.0
, COVID added a lot of stress and work has been busy, to say the least. I'm behind on all of my OSS repos, TSDX is actually the most maintained (but needs a lot more attention) 😕v0.14.0
will be the next release, which will be a breaking change mostly due to updating dependencies' majors. I held back on it to get more intov0.13.x
before getting busy, but unfortunately I wasn't able to get to all the changes I wanted to into it, but v0.14.0 has been waiting long enoughWishing everyone well! Please stay safe and please do your part to follow public health guidelines!
✊ Quoting from a Chromium release ✊ :
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.