Software development, I think, is a very specific situation because unlike a lot of other jobs there are a lot of people out there who can give a good interview and might even have even memorized enough tricks to pass a short competency test, but when it comes down to it can't actually develop software. To an extent you should always feel as an SDEV that you begin a job on a probationary period. The companies that spell it out might have been burned in the past, but I've definitely worked at places where people were given a month or even six months to work out whatever they were going to do before they were let go, even with no probationary period in place.
I think that if you can write code then you're probably OK, and if you can't then you probably are not. Otherwise, I would use other criteria than this one to determine if the place is a good fit for you. If it seems overly competitive or there are signs that management is not nice (perhaps there's a high turnover rate, maybe it's just a vibe you get during the interview) then that "probationary period" might in fact be a big red flag, but even there the red flag isn't so much in the probation, it's
I will say that if you're familiar with a particular stack and you're moving out of that particular stack, you might want to make clear where your strengths and weaknesses are heading in. If a company has that "let's see how this person does for 3 months before granting them a FT position" outlook at the forefront, you positioned yourself as a front-end ace in the interview, and you struggle off the bat with a website set up in Angular, then that's going to look a lot worse than if you admit that you don't have experience with that particular framework. The flip side of that is that the company may decide not to hire you in favor of someone else who does claim to be an ace (who in turn may not be truthful). Good salesmanship is key here.
The final thing that I would be most concerned about in your position is if the company in question is hiring, say, 2 devs to fill one slot with the intention that the poorer performing one will be shown the door. Honestly, I have not really seen this happen in practice - good devs are too hard to find to alienate one by doing that, and besides, companies tend to be too cheap to pay for 2 guys for 3 months knowing that they really only want one of them - but it's probably a thing I'd stay away from personally.