Update sass 1.49.9 → 1.83.0 (minor)

[depfu]

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ sass (1.49.9 → 1.83.0) · Repo · Changelog

Release Notes

Too many releases to show here. View the full release notes.

↗️ immutable (indirect, 4.2.4 → 5.0.3) · Repo · Changelog

Release Notes

5.0.3

What's Changed

• Fix List.VNode.removeAfter() / removeBefore() issue on some particular case by @alexvictoor in #2030

New Contributors

• @alexvictoor made their first contribution in #2030

Full Changelog: v5.0.2...v5.0.3

5.0.2

Changed

• Fix wrong path for esm module after fix in 5.0.1

Full Changelog: v5.0.1...v5.0.2

5.0.1

What's Changed

Fixes

• Fix circular dependency issue with ESM build by @iambumblehead in #2035

Internal

• Upgrade TSTyche by @mrazauskas in #2034

Full Changelog: v5.0.0...v5.0.1

5.0.0

Breaking changes

To sum up, the big change in 5.0 is a Typescript change related to Map that is typed closer to the JS object. This is a huge change for TS users, but do not impact the runtime behavior. (see Improve TypeScript definition for Map for more details)

Other breaking changes are:

[BREAKING] Remove deprecated methods:

Released in 5.0.0-rc.1

• Map.of('k', 'v'): use Map([ [ 'k', 'v' ] ]) or Map({ k: 'v' })
• Collection.isIterable: use isIterable directly
• Collection.isKeyed: use isKeyed directly
• Collection.isIndexed: use isIndexed directly
• Collection.isAssociative: use isAssociative directly
• Collection.isOrdered: use isOrdered directly

[BREAKING] OrdererMap and OrderedSet hashCode implementation has been fixed

Released in 5.0.0-rc.1

Fix issue implementation of hashCode for OrdererMap and OrderedSet where equal objects might not return the same hashCode.

Changed in #2005

[BREAKING] Range function needs at least two defined parameters

Released in 5.0.0-beta.5

Range with undefined would end in an infinite loop. Now, you need to define at least the start and end values.

If you need an infinite range, you can use Range(0, Infinity).

Changed in #1967 by @jdeniau

[Minor BC break] Remove default export

Released in 5.0.0-beta.1

Immutable does not export a default object containing all it's API anymore.
As a drawback, you can not immport Immutable directly:

- import Immutable from 'immutable';
+ import { List, Map } from 'immutable';
- const l = Immutable.List([Immutable.Map({ a: 'A' })]);

+ const l = List([Map({ a: 'A' })]);

If you want the non-recommanded, but shorter migration path, you can do this:

- import Immutable from 'immutable';
+ import * as Immutable from 'immutable';
const l = Immutable.List([Immutable.Map({ a: 'A' })]);

[TypeScript Break] Improve TypeScript definition for Map

Released in 5.0.0-beta.1

If you do use TypeScript, then this change does not impact you : no runtime change here.
But if you use Map with TypeScript, this is a HUGE change !
Imagine the following code

const m = Map({ length: 3, 1: 'one' });

This was previously typed as Map<string, string | number>

and return type of m.get('length') or m.get('inexistant') was typed as string | number | undefined.

This made Map really unusable with TypeScript.

Now the Map is typed like this:

MapOf<{
    length: number;
    1: string;
}>

and the return type of m.get('length') is typed as number.

The return of m.get('inexistant') throw the TypeScript error:

Argument of type '"inexistant"' is not assignable to parameter of type '1 | "length"

If you want to keep the old definition

This is a minor BC for TS users, so if you want to keep the old definition, you can declare you Map like this:

const m = Map<string, string | number>({ length: 3, 1: 'one' });

If you need to type the Map with a larger definition

You might want to declare a wider definition, you can type your Map like this:

type MyMapType = {
  length: number;
  1: string | null;
  optionalProperty?: string;
};
const m = Map<MyMapType>({ length: 3, 1: 'one' });

Keep in mind that the MapOf will try to be consistant with the simple TypeScript object, so you can not do this:

Map({ a: 'a' }).set('b', 'b');
Map({ a: 'a' }).delete('a');

Like a simple object, it will only work if the type is forced:

Map<{ a: string; b?: string }>({ a: 'a' }).set('b', 'b'); // b is forced in type and optional
Map<{ a?: string }>({ a: 'a' }).delete('a'); // you can only delete an optional key

Are all Map methods implemented ?

For now, only get, getIn, set, update, delete, remove, toJS, toJSON methods are implemented. All other methods will fallback to the basic Map definition. Other method definition will be added later, but as some might be really complex, we prefer the progressive enhancement on the most used functions.

Fixes

• Fix type inference for first() and last() #2001 by @butchler
• Fix issue with empty list that is a singleton #2004 by @jdeniau
• Map and Set sort and sortBy return type #2013 by @jdeniau

Internal

• [Internal] Migrating TS type tests from dtslint to TSTyche #1988 and #1991 by @mrazauskas.
  Special thanks to @arnfaldur that migrated every type tests to tsd just before that.
• [internal] Upgrade to rollup 3.x #1965 by @jdeniau
• [internal] upgrade tooling (TS, eslint) and documentation packages: #1971, #1972, #1973, #1974, #1975, #1976, #1977, #1978, #1979, #1980, #1981

Full Changelog: v4.3.3...v5.0.0

4.3.7

What's Changed

• Fix issue with slice negative of filtered sequence by @jdeniau in #2006

Full Changelog: v4.3.6...v4.3.7

4.3.6

What's Changed

• Fix Repeat().equals(undefined) incorrectly returning true by @butchler in #1994

Internals

• change youtube image by @jdeniau in #1973
• Upgrade eslint and ignore no-constructor-return rule for actual constructors by @jdeniau in #1974
• upgrate documentation website to next 14 by @jdeniau in #1975
• start migrating to nextjs app router by @jdeniau in #1976
• upgrade next sitemap by @jdeniau in #1978

New Contributors

• @butchler made their first contribution in #1994

Full Changelog: v4.3.5...v4.3.6

4.3.5

What's Changed

• Fix Set.fromKeys types with Map constructor in TS 5.0 by @jdeniau in #1971
• upgrade to TS 5.1 by @jdeniau in #1972
• fix dist-stats command by @jdeniau in #1964
• fix Read the Docs link on readme by @joshding in #1970

New Contributors

• @joshding made their first contribution in #1970

Full Changelog: v4.3.4...v4.3.5

4.3.4

What's Changed

• Rollback toJS type due to circular reference error by @jdeniau in #1958

Full Changelog: v4.3.3...v4.3.4

4.3.3

What's Changed

• [typescript] manage to handle toJS circular reference. #1932 by @jdeniau
• [doc] Add install instructions for pnpm and Bun #1952 by @colinhacks and #1953 by @menglingyu659

New Contributors

• @colinhacks made their first contribution in #1952
• @menglingyu659 made their first contribution in #1953

Full Changelog: v4.3.1...v4.3.3

4.3.2

What's Changed

• Fix isOrderedSet type by @jdeniau in #1948

Full Changelog: v4.3.1...v4.3.2

4.3.1

What's Changed

• remove unused exports by @jdeniau in #1928
• Faster and implementation of some by @jdeniau in #1944

Full Changelog: v4.3.0...v4.3.1

4.3.0

What's Changed

• TS: update method may return undefined by @jdeniau in #1933
• DOCS: wrong link in README by @BilderLoong in #1938
• Fix fromJS declaration for greater compatibility by @jdeniau in #1936
• Introduce Comparator and PairSorting by @giancosta86 in #1937

New Contributors

• @BilderLoong made their first contribution in #1938
• @giancosta86 made their first contribution in #1937

Full Changelog: v4.2.4...v4.3.0

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

🆕 @​parcel/watcher (added, 2.5.0)

🆕 @​parcel/watcher-android-arm64 (added, 2.5.0)

🆕 @​parcel/watcher-darwin-arm64 (added, 2.5.0)

🆕 @​parcel/watcher-darwin-x64 (added, 2.5.0)

🆕 @​parcel/watcher-freebsd-x64 (added, 2.5.0)

🆕 @​parcel/watcher-linux-arm-glibc (added, 2.5.0)

🆕 @​parcel/watcher-linux-arm-musl (added, 2.5.0)

🆕 @​parcel/watcher-linux-arm64-glibc (added, 2.5.0)

🆕 @​parcel/watcher-linux-arm64-musl (added, 2.5.0)

🆕 @​parcel/watcher-linux-x64-glibc (added, 2.5.0)

🆕 @​parcel/watcher-linux-x64-musl (added, 2.5.0)

🆕 @​parcel/watcher-win32-arm64 (added, 2.5.0)

🆕 @​parcel/watcher-win32-ia32 (added, 2.5.0)

🆕 @​parcel/watcher-win32-x64 (added, 2.5.0)

🆕 detect-libc (added, 1.0.3)

🆕 node-addon-api (added, 7.1.1)

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[depfu]

Closed in favor of #43.