linaria
mapbox-gl-js
Our great sponsors
linaria | mapbox-gl-js | |
---|---|---|
46 | 13 | |
11,182 | 10,697 | |
0.9% | 0.7% | |
8.4 | 9.8 | |
22 days ago | 8 days ago | |
TypeScript | JavaScript | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
linaria
-
How we improved page load speed for Next.js ecommerce website by 1.5 times
The code duplication occurred due to disabling the default code splitting algorithm in Next.js. Previous developers used this approach to make Linaria work, which is designed to improve productivity. However, disabling code splitting led to a decrease in performance.
-
An Overview of 25+ UI Component Libraries in 2023
KumaUI : Another relatively new contender, Kuma uses zero runtime CSS-in-JS to create headless UI components which allows a lot of flexibility. It was heavily inspired by other zero runtime CSS-in-JS solutions such as PandaCSS, Vanilla Extract, and Linaria, as well as by Styled System, ChakraUI, and Native Base. ### Vue
-
Why Tailwind CSS Won
I like Linaria [0] because your IDE typechecks your styles and gives you autocomplete/intellisense when typing styles. With Tailwind you have to look everything up in docs because it's all strings, not importable constants. Leads to a lot of bugs from typos that aren't a thing with type checked styles.
[0] https://github.com/callstack/linaria
-
I've decided to go back to using the Pages Router for now (long post)
And if you're wondering why I'm not using something like Linaria or some other runtime-less CSS-in-JS tool, it's simply because I don't want to have to spend my time setting things up and working around stuff and all that jazz. I just want something that works, and I've already got a personal scaffold for getting SC to work out of the box with Next, so, right now, it's either that or sticking to CSS/SCSS/SASS. For me, that is. I know it's such a small thing, but, honestly, one less headache for me is 2 steps forward.
- What's the best option these days for CSS in JS?
-
How bad is it to use CSS-in-JS with regards to the future of React?
I know that there are solutions that generate static css files (like vanilla-extract or linaria), but neither of them work with app router currently (1, 2).
-
JSS vs Styled Components? and why?
If you really want tighter interaction with JS, try a zero-runtine solution like linaria
-
What is the best CSS framework to use with React? why?
https://github.com/callstack/linaria is objectively the best. It's 100% styled component compatible, but with zero runtime which not only makes it substantially faster, but also makes it easy to do things like server side rendering, etc.
-
Why is tailwind so hyped?
tags inside SFCs are typically injected as native
</code> tags during development to support hot updates. <strong>For production they can be extracted and merged into a single CSS file.</strong></p> </blockquote> <p>There are also 3rd party CSS libs that do the same thing such as <a href="https://linaria.dev/">linaria</a>, <a href="https://vanilla-extract.style/">vanilla-extract</a>, and <a href="https://compiledcssinjs.com/">compiled CSS</a>. Which can be used in the event you're stuck with something that doesn't have baked in support via SFC formats (looking at you React).</p> <p>These are my preferred ways of handing it.</p> <ol> <li>Tailwind</li> </ol> <p>Option 2 is tailwind, which works backwards.</p> <p>That is, instead of the above with extraction where you write the styles, and the framework or libs extract them and replace them with class names, it's the other way around.</p> <p>You're writing class names first (which are essentially aggregated CSS property-values) which then generate and/or reference styles.</p> <p>It has the advantage of being easy to write (assuming you've got editor LSP, linting, etc), but as you've discovered, it's difficult to read / can get really messy really fast.</p> <p>As far as all the other claims on the Tailwind site, it's all marketing, at least 80% bullshit.</p> </div>
- Individual css for every component?
mapbox-gl-js
-
Brave browser simplifies its fingerprinting protections
Good. Brave's fiddling with WebGL causes >50% of my bug reports from 1% of users.
[1] https://github.com/mapbox/mapbox-gl-js/issues/10518
[2] https://github.com/mapbox/mapbox-gl-js/issues/8377
-
What is the tech stack for MapGinie dot IO?
Laravel and Mapbox GL JS
- [OC] 20 years of forest loss in South East Asia - INTERACTIVE
-
Getting Started with MapLibre GL JS
It originated as an open-source fork of Mapbox-gl-js before they switched to a non-open-source license on 8th December 2020.
-
75% of Nova Scotia's population lives in the red areas
Do you have programming skills? MapboxGL JS is a great library for stuff like this, you can really easily add a layer of GeoJSON data to a map. If you're looking for something less technical Google map lets you create custom maps where you can add a bunch of pins.
-
Experimenting with Mapbox GL JS's upcoming globe projection
From the latest commits (not released/stable yet): git clone https://github.com/mapbox/mapbox-gl-js.git yarn install yarn run build-prod-min yarn run build-css Then use the generated mapbox-gl.js and mapbox-gl.css files. See CONTRIBUTING.md for more details.
-
Reimagining projections for the interactive maps era
> too bad it doesn't come with some code
Mapbox changed the license of their code last year I think to a proprietary one. https://github.com/mapbox/mapbox-gl-js/blob/main/LICENSE.txt
It requires a mapbox user license with billing enabled to use this code, let alone make modifications. But the source is viewable on github.
- I built an app that maps out crime statistics
-
MapLibre GL is a free and open-source fork of mapbox-gl-JS
The software stopped being open source from v2 onwards. The new licence makes it merely shared source.
This GitHub issue where this change is announced provides a number of more in-depth explanations why this is a bad thing for most users of the software: https://github.com/mapbox/mapbox-gl-js/issues/10162
-
Ask HN: What Are You Working On?
It's a bummer mapbox isn't open source anymore, now you're (and lots of other peoplare) are stuck pre-2.0.0 :(
https://github.com/mapbox/mapbox-gl-js/blob/main/CHANGELOG.m...
What are some alternatives?
emotion - 👩🎤 CSS-in-JS library designed for high performance style composition
maplibre-gl-js - MapLibre GL JS - Interactive vector tile maps in WebGL2
Tailwind CSS - A utility-first CSS framework for rapid UI development.
cesium - An open-source JavaScript library for world-class 3D globes and maps :earth_americas: [Moved to: https://github.com/CesiumGS/cesium]
styled-components - Visual primitives for the component age. Use the best bits of ES6 and CSS to style your apps without stress 💅
h3 - Hexagonal hierarchical geospatial indexing system
vanilla-extract - Zero-runtime Stylesheets-in-TypeScript
ffprobe-wasm - A Web-based FFProbe. Powered by FFmpeg, Vue and Web Assembly!
classnames - A simple javascript utility for conditionally joining classNames together
martin - Blazing fast and lightweight PostGIS, MBtiles and PMtiles tile server, tile generation, and mbtiles tooling.
React CSS Modules - Seamless mapping of class names to CSS modules inside of React components.
tangram - WebGL map rendering engine for creative cartography