Closed sneridagh closed 2 weeks ago
Name | Link |
---|---|
Latest commit | 4ac8e2e5c1ff5e221e41542fe00d3f3cb511583d |
Latest deploy log | https://app.netlify.com/sites/plone-components/deploys/6729072b1deec6000843f296 |
@davisagli just added some more background in the description.
@stevepiercy no, always in automated build processes, but they could see when it failed.
BTW, @davisagli @stevepiercy in the next days, probably I will be replacing (if possible) parcel
with tsup
in all our builds
We are having problems in some setups in macos where
parcel
errors with a segmentation fault and we found also some weird errors related with it inpnpm
lock, where the lock keeps updating because of it (apparently, their entries in the lock keep cycling infinitely). In addition, the resultant code has some weird names with a looong hash that end up in the dev tools. Then I also learned thattsup
is more pure with their outputs and it was the recommended setup, see:https://www.totaltypescript.com/how-to-create-an-npm-package
Totally worth it from top to bottom.
I also fixed the remaining types that forced us to
||true
in the build output. So overall this PR improves the current situation, in a non-breaking way.