If i correct understood you, you want to use relative imports inside alias directory. This is possible, you may check test about it github.com/vitonsky/…/alias.test.ts#L36-L40
Current plugin is just about force use aliases instead of relative paths (and back for deprecated aliases).
If you need to sort imports, you may try rule simple-import-sort/imports from github.com/…/eslint-plugin-simple-import-sortIt is very flexible, so you may customize your own groups. For instance, you may group aliases in one group and relative imports to another group. Check their docs
Exactly! I see how a mindset “we delivered (shit) quickly” successfully reproduces itself, over and over in a lot of companies.
I think the actual reason is that business want to make money on promises right here right now. Business promises a lot of features to investors give money, and then business implement a lot of (shit) features. And then they continue kinda “okay, features broken, give us more money and we will fix it”.
I hope you’re right. The more people will save it, the more chances we have to find the source code later, or even find the community who will maintain the fork.
You can see the code of extensions, but it may be minimized, so it hard to known what the code do.
Extensions with label “Recommended” are pass the manual review of Firefox moderators, so you can trust them more than addons with no this label. However you still should keep in mind that any extension developer may be victim of complex scam attack.
The most probable reason usually is a not enough funding the developers
Developer spend time on maintaining the project but users does not donate them
Scammers offer to developer some integrations that not looks too suspicious and allow them to earn some money
Developer agree offer and after some time scammers enables malware to hack extension users
To minimize the possibility of hijacking addons by scammers, we have to:
conduct background check before install extension
ensure the extension have github with open source code and developer are real person
ensure development are active and developer have high engineering skill, check them respond on feedback and issues
donate the developer if you like the product, to motivate them keep distance of scammers offers
If you think a Object Oriented Programming is a framework, then you can think about BEM like a framework too. But a correct word is a methodology. A “framework” have too generic meaning.
Methodology gives us a methods how to improve software quality. This methods like an interfaces in programming that we must implement as programmers
Keep the logs for retrospective analysis (vitonsky.net)
eslint-plugin-paths: A plugin for ESLint, to force use paths aliases from tsconfig (github.com)
Decision logs (vitonsky.net)
Nintendo forces to close the opensource Nintendo Switch emulator "yuzu-emu". It's time to clone their source code (mastodon.social)
Refusing TypeScript is a signal that you don't care about code quality (vitonsky.net)
Browser extensions spy on you, even if its developers don't (vitonsky.net)
Linguist, an ultimate translation browser extension (vitonsky.net)
cross-posted from: programming.dev/post/1927197...
Linguist, an ultimate translation browser extension (vitonsky.net)
cross-posted from: programming.dev/post/1924228...
BEM methodology is not about CSS (vitonsky.net)
cross-posted from: programming.dev/post/1923251...