Alexander Plavin

Probably same as https://github.com/JuliaData/CSV.jl/issues/1012

Probably, `TestEnv.jl` will help: its goal is exactly to activate the test environment in a consistent way. I personally never see the need to write > `julia --project=test -e 'import...

> provide a constructor from fields no matter what Yes, nice to have it whenever possible. Ie, `constructorof(array)(getfields(A))` won't work on 1.10- because it doesn't have any fields, but will...

[See also](https://aplavin.github.io/PlutoUIExtra.jl/src/slider.html) – fully generic slider styling in PlutoUIExtra.jl (+PR here in PlutoUI.jl https://github.com/JuliaPluto/PlutoUI.jl/pull/258). Works for vertical and whatever else you might want: 

I only searched over open issues, and was surprised to see this wasn't reported before :) Now I see that it was indeed. > There hasn't been a chorus of...

Thanks, I understand it's nontrivial to fix while keeping other parts of user experience. Still, I believe making packages installable is important, and will only become more important in the...

Juliahub search indicates that quite a few packages call get_extension in their extensions, so maybe this bug manifests itself somewhere else as well. Or maybe not, depends on the order...

> AFAIK get_extension is internal (its also written in its docstring) and is subject to change It's mentioned and explained in Pkg docs, https://pkgdocs.julialang.org/v1/creating-packages/. Afaiu, in 1.10 and earlier this...

Indeed, you are right, I wasn't looking carefully enough! Still not 100% used to seeing "big scary errors" that are practically just warnings :)

Indeed, maybe it slipped through the cracks over time... Anyway, I confirm that with `__precompile__(false)` everything loads fine and functions work afterwards.