StyleShit

36 posts

StyleShit banner
StyleShit

StyleShit

@StyleShit_

⚡️ Full-Stack Developer 🎤 Public Speaker 💖 CSS artist 🎨 https://t.co/Lshf20dBh7 👨‍💻 https://t.co/poa8RD1mpo

Entrou em Mart 2022
250 Seguindo8 Seguidores
StyleShit
StyleShit@StyleShit_·
@kettanaito Ah sorry, I wasn't clear I'm not saying that things are missing, I'm using MSW and it's awesome! I tough you're asking how to advertise it in X so more people will be familiar with it 😅
English
1
0
1
14
Artem Zakharchenko
Artem Zakharchenko@kettanaito·
Thanks! Short comparisons with other libraries: mswjs.io/docs/comparison (literally cannot do shorter without losing context). You can use everything you see in the docs in tests 1-1. That's one of the selling points of MSW. Your mocks stay the same. We've got a bunch of full-app examples as well: github.com/mswjs/examples Anything else that's missing?
English
1
0
1
122
Artem Zakharchenko
Artem Zakharchenko@kettanaito·
Should I talk more about MSW? I almost never advertise it anymore, but it pains me to see so many devs missing out on it and (rightfully) complaining that API mocking is a mess. The problem that we solved. What would you like to hear more about?
English
13
3
77
8.7K
Ori Livni
Ori Livni@oriSomething·
I’m announcing Slopreact. It’s like Preact, but only 3,000MB
English
3
0
7
212
Paweł Błaszczyk
Paweł Błaszczyk@pawelblaszczyk_·
@kysely_ 5.9, in my experience the only thing that slows me down from updating is stuff like TS ESLint support 😄
English
2
0
4
97
kysely
kysely@kysely_·
what is the *lowest* typescript version being used in actively developed / maintained projects you own or contribute to?
English
3
1
4
2.1K
StyleShit
StyleShit@StyleShit_·
@thymikee @sebastienlorber But what about cases you have to use it? e.g., running in the context of the base repo It's a security risk, but it still does make sense not to expose secrets in workflows coming from forks
English
0
0
0
9
Seb ⚛️ ThisWeekInReact.com
Seb ⚛️ ThisWeekInReact.com@sebastienlorber·
⚠️ GitHub Actions + "pull_request_target" Another large supply chain attack that starts from this. I hope this time it serves as a lesson for anyone using this workflow trigger
Seb ⚛️ ThisWeekInReact.com tweet media
Andrej Karpathy@karpathy

Software horror: litellm PyPI supply chain attack. Simple `pip install litellm` was enough to exfiltrate SSH keys, AWS/GCP/Azure creds, Kubernetes configs, git credentials, env vars (all your API keys), shell history, crypto wallets, SSL private keys, CI/CD secrets, database passwords. LiteLLM itself has 97 million downloads per month which is already terrible, but much worse, the contagion spreads to any project that depends on litellm. For example, if you did `pip install dspy` (which depended on litellm>=1.64.0), you'd also be pwnd. Same for any other large project that depended on litellm. Afaict the poisoned version was up for only less than ~1 hour. The attack had a bug which led to its discovery - Callum McMahon was using an MCP plugin inside Cursor that pulled in litellm as a transitive dependency. When litellm 1.82.8 installed, their machine ran out of RAM and crashed. So if the attacker didn't vibe code this attack it could have been undetected for many days or weeks. Supply chain attacks like this are basically the scariest thing imaginable in modern software. Every time you install any depedency you could be pulling in a poisoned package anywhere deep inside its entire depedency tree. This is especially risky with large projects that might have lots and lots of dependencies. The credentials that do get stolen in each attack can then be used to take over more accounts and compromise more packages. Classical software engineering would have you believe that dependencies are good (we're building pyramids from bricks), but imo this has to be re-evaluated, and it's why I've been so growingly averse to them, preferring to use LLMs to "yoink" functionality when it's simple enough and possible.

English
2
0
11
5.6K
StyleShit
StyleShit@StyleShit_·
@oriSomething People think that if it's on npm it's for sure good code with the ideal implementation
English
0
0
0
203
Ori Livni
Ori Livni@oriSomething·
There is a React utilities library with 2 millions weekly downloads that many of its hooks aren’t concurrent safe, some don’t even work in strict mode, and most other hooks are sub-optimal solution. But devs will explain: you must use React because of the ecosystem
English
5
2
25
4K
StyleShit
StyleShit@StyleShit_·
@sanxiaozhizi Wait, what? I just needed this few hours ago! 🤯 I gotta plan my wishes better
English
0
0
1
197
Kevin Deng 🦋 @sxzz.dev
Kevin Deng 🦋 @sxzz.dev@sanxiaozhizi·
🚀 tsdown 0.21.4 just dropped. CSS Modules are now supported. Also, the `tsdown-migrate` skill lets your agent auto-migrate from tsup to tsdown. ❯ npx skills add rolldown/tsdown --skill tsdown-migrate tsdown.dev/guide/skills
English
1
11
130
8.6K
Ori Livni
Ori Livni@oriSomething·
אין דבר שמעציב אותי כמו לראות פרוייקט עם package-lock.json
עברית
11
0
42
7.7K
StyleShit retweetou
Firefox for Web Developers
Firefox for Web Developers@FirefoxWebDevs·
JavaScript Iterator․zip landed in Firefox 148, making it simple to loop over multiple things at the same time. Here's how it works:
English
6
19
216
11.8K
StyleShit
StyleShit@StyleShit_·
@oriSomething AI has always been pretty bad with more than some simple types (at least in my experience) But what's the issue? Now I'm curious
English
1
0
0
17
Ori Livni
Ori Livni@oriSomething·
I don't believe Opus-4.6 and GPT-codex-5.3 failed to solve some TypeScript issue we had with some library. I think we should train the models on Polish writings to improve their TypeScript capabilities
English
3
0
7
276
Rebane
Rebane@rebane2001·
i built an entire x86 CPU emulator in CSS (no javascript) you can write programs in C, compile them to x86 machine code with GCC, and run them inside CSS
English
331
1.1K
10.2K
1M
StyleShit
StyleShit@StyleShit_·
@kettanaito IMO both are fine as long as it's documented. I think it comes down to whether you want to allow overrides or not (spreading multiple handlers array for example, kinda similar to object merging)
English
1
0
1
49
Artem Zakharchenko
Artem Zakharchenko@kettanaito·
What do you expect GET localhost/resource to return in this case? Note: exceptions in resolvers are coerced into special 500 mocked responses (ala similar exception occurring on the real server).
Artem Zakharchenko tweet media
English
3
0
2
1.5K
Ori Livni
Ori Livni@oriSomething·
prettier (50s) -> oxfmt (12s)
English
3
2
99
7.5K
StyleShit
StyleShit@StyleShit_·
@ryanflorence Start & end are positions in the HTML string? What's the advantage of this approach compared to an element reference?
English
0
0
1
161
Ryan Florence
Ryan Florence@ryanflorence·
Something pretty cool about Remix 3 is you can render a root in-between two elements, even comments <html> <!-- start --> <head /> <body /> <!-- end --> </html> createRoot([start, end]) .render(<><Head/><Body/></>)
English
2
0
26
4.3K
StyleShit retweetou
Josh Goldberg 🦋
Josh Goldberg 🦋@JoshuaKGoldberg·
Flint is a fast, friendly new experimental linter. It tries out a *ton* of things different from the status quo. If you're interested in how a new web linter could work, this deep dive is for you! P.S. we're always looking for new contributors 😉 🔗👇
English
2
3
14
2.1K
StyleShit
StyleShit@StyleShit_·
@boshen_c @mileswjohnson Why? It was a pretty straightforward setup for me (except the initial publish that still requires a token for some reason?)
English
0
0
0
78
Boshen
Boshen@boshen_c·
@mileswjohnson Trusted publish, be prepared for the half day of waste time.
English
4
0
25
2.1K
Miles . 마일스
Miles . 마일스@mileswjohnson·
Because of the npm token changes, what's the best way to publish packages from CI/CD now?
English
2
0
4
2.2K
StyleShit retweetou
Taylor Otwell
Taylor Otwell@taylorotwell·
A few things I've noticed as all devs write code with AI. When you write foundational / architectural code of a new project by hand, you "feel" the code pushing back if your abstraction isn't right. You feel when something is harder than it should be. The code is telling you it's not in the right shape. Good engineers are sensitive to this. When you're using an LLM, you keep pushing right through this in a way that feels like you're making progress, and it may even be directionally correct in a sense, but the underlying foundation of it all is actually bad in a way that either kills progress of the LLM later as it buckles under the complexity it has created or destroys your ability to maintain the code long term. Related to this, I see a general restlessness with just sitting and thinking about a problem for a while. As I've been working on a new library here at Laravel, there have been days where it feels like I mainly just stare at my screen thinking about something. When Claude Code is at your fingertips, it's tempting to just start yapping into the terminal and watching code come out the other end. Again, directionally correct in some ways, but often doesn't land on the elegant solution that is waiting to be discovered.
English
270
473
3.9K
488.3K