check 5.x #2011
check 5.x #2011
Conversation
Co-authored-by: Michael Bullington <michael.bullington@mapbox.com>
…g modules (#1888) Co-authored-by: Taylor Clay <tclay@atlassian.com> Co-authored-by: Julien Deniau <julien.deniau@gmail.com>
* Upgrade eslint and ignore no-constructor-return rule for actual constructors (#1974) * Upgrade eslint and ignore no-constructor-return rule for actual constructors * ignore eslint-next for now * upgrate documentation website to next 14 (#1975) * upgrate to next 12 * next 13 * migrate links * next 14 * deactivate eslint for documentation once again * Fix title warning. See vercel/next.js#38256 * start migrating to nextjs app router (#1976) * upgrade next sitemap (#1978)
* replace tslint by typescript-eslint * remove tslint config file and comments * Fix eslint issue in src directory * Migrate simple eslint rules in __test__ directory * use stricter types in __tests__ directory * Fix or ignore all eslint issues in website directory * Ignore eslint report in main immutable.d.ts file for now
…nto butchler-first-last-types
* 5.0.0-rc.1 * changelog
|
Hi @leebyron , I'd like to merge this huge 5.x branch, but I'd like not to squash all this (it contains links to PR etc.)
I did allow "Allow merge commits" and "Allow rebase merging" in the "general" settings, but the "merge" option is still disabled in the PR.
I tried merging in command line too, but I got: Thank you. |
|
Thank you for this great package. The rollup process generates minified and un-minified "umd" modules that are less useful these days. Please consider exporting minified esm instead. |
|
Theoretically, the "module" key of package.json does target an ESM build. I'm not really confident with releasing a non-umd build as there is a lot of users of immutable. |
Create a PR to check that all 5.0.0 code is OK before merging in main.