#LanguageOptions
Hey sorry to drive-by, but I think you can simplify that:
* tseslint.config returns a typed object
* combine { files }, { languageOptions }
* use tseslint.config extends instead of manual spreads in two objects
* tsParser is already set by tseslint.configs.*

www.typescriptlang.org/play/#code/J...
TS Playground - An online editor for exploring TypeScript and JavaScript
The Playground lets you write TypeScript or JavaScript online in a safe and sharable way.
www.typescriptlang.org
December 8, 2024 at 9:42 PM
In Stylelint 17.6.0, we added support for custom units in `languageOption`, which will apply to rules like `declaration-property-value-no-unknown`.

Release notes: github.com/stylelint/st...

Docs: stylelint.io/user-guide/c...
Release 17.6.0 · stylelint/stylelint
It adds support for extending units in languageOptions, which then apply to rules like declaration-property-value-no-unknown, and fixes 2 bugs. Added: support for extending units to languageOption...
github.com
March 27, 2026 at 9:31 AM
It's best to configure `languageOptions.directionality` if you use the rules directly.

E.g. For a top-to-bottom, left-to-right language like English:

```
languageOptions: {
directionality: {
block: "top-to-bottom",
inline: "left-to-right",
},
}
```

Docs: stylelint.io/user-guide/c...
Configuring | Stylelint
Stylelint expects a configuration object.
stylelint.io
May 3, 2026 at 7:10 PM
For example, adding `--rpx` as a custom `<length>`:

```
export default {
extends: ["stylelint-config-standard"],
languageOptions: {
syntax: {
units: { length: ["--rpx"] }
}
},
};
```

Will now allow: `a { margin: 10--rpx; }`

While still catching: `a { margin: 10ms; }`
March 27, 2026 at 9:31 AM
I had some issues connecting eslint-plugin-react-hooks to eslint@9.x
After a few hours, I figured out what it was missing. I had to explicitly pass rules and react's plugin `languageOptions` into `tslint.config()` #eslint #react #reactHooks
November 14, 2024 at 10:28 AM
Stylelint の新しい languageOptions オプション、良さそう
March 3, 2025 at 4:16 AM
Netflix expands language options for TV viewers
NFLX hereremove ads Latest comments Install Our AppScan QR code to install app Google Play App Store Blog Mobile Portfolio Widgets About Us Advertise Help & Support Authors Risk Disclosure: Trading in financial instruments and/or cryptocurrencies involves high risks including the risk of losing some, or all, of your investment amount, and may not be suitable for all investors. Prices of cryptocurrencies are extremely volatile and may be affected by external factors such as financial, regulatory or political events. Trading on margin increases the financial risks. Before deciding to trade in financial instrument or cryptocurrencies you should be fully informed of the risks and costs associated with trading the financial markets, carefully consider your investment objectives, level of experience, and risk appetite, and seek professional advice where needed. Fusion Media would like to remind you that the data contained in this website is not necessarily real-time nor accurate. The data and prices on the website are not necessarily provided by any market or exchange, but may be provided by market makers, and so prices may not be accurate and may differ from the actual price at any given market, meaning prices are indicative and not appropriate for trading purposes. Fusion Media and any provider of the data contained in this website will not accept liability for any loss or damage as a result of your trading, or your reliance on the information contained within this website. It is prohibited to use, store, reproduce, display, modify, transmit or distribute the data contained in this website without the explicit prior written permission of Fusion Media and/or the data provider. All intellectual property rights are reserved by the providers and/or the exchange providing the data contained in this website. Fusion Media may be compensated by the advertisers that appear on the website, based on your interaction with the advertisements or advertisers.
www.investing.com
April 2, 2025 at 2:51 PM
2. For some reason, ESLint couldn't find tsconfig.json in my project. I have a monorepo with a bunch of packages. Each package contains its own tsconfig.json. Maybe it is the cause of the issue.

The fix is simple. Set languagesOptions.parserOptions.tsconfigRootDir to import.meta.dirname
December 23, 2025 at 8:42 PM
mbx-eslint-config looks like this:

```
import stylisticJs from '@stylistic/eslint-plugin-js';
import globals from "globals";

export default {
configs: {
recommended: {
name: 'mbx/recommended',

plugins: {
'@stylistic/js': stylisticJs,
},

languageOptions: {
sourceType: "module",
globals: { /* […]
Original post on puz.fun
puz.fun
April 1, 2025 at 6:09 PM