Comments (6)
yeah or just get a major version like
#import "preview/pkg:1.*"
That way you are not getting major API changes and still bug fixes
from packages.
I can definitely see how that's desirable in certain situations as well, but there really are times when I just want the latest and greatest from a package (likely because I'm just goofing around); and don't want to think about what the latest version is.
I guess a way to make this consistent with your suggestion is @preview/pkg:*
, which; while I'm not against, does seem a little more ambiguous than latest
.
Also with yours; is there any guarantee that typst will pick the latest version it knows about? To me it looks more like 'pick any matching version; I don't care'
from packages.
i mean if there is a new major version of a package you can expect API changes so latest
could endup breaking your build, but i can see why someone would like to just get the latest
from packages.
I think good editor support for autocompleting the latest version is better. If we support this, then people will just use it all the time and we'll get lots of breakage down the road.
from packages.
That sounds sensible, good editor support is always nice
from packages.
Okay, I'm going to close this then.
from packages.
Related Issues (20)
- I think graph_plots seem to have issues with too large numbers in Visual Studio Code HOT 1
- How to: reference with @ HOT 2
- lovelace does not display captions correctly HOT 2
- circular arrows for self-pointing HOT 1
- Documentation Colorful-Boxes is incorrect HOT 1
- UDP Protocol typo
- typo in units.scv HOT 2
- Link to packages original github from the webpage HOT 2
- Macro in column operator increase newlines HOT 2
- Validate package repo link exists HOT 2
- Template containing different flavors HOT 1
- Tiaoma readme typo. Should I edit it inplace or publish a new version? HOT 1
- Description for cumcm-muban includes link to non-free font HOT 3
- Large packages in the current git-based package system? HOT 1
- system wide local packages HOT 2
- Allowing for a display name parameter in `typst.toml` for cleaner package listings in Typst Universe HOT 1
- Is it Ok to use git submodule for template in a package? HOT 1
- Invalid package folder is skipped without error
- Git submodules instead of monorepo HOT 1
- Discipline search doesnโt work HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. ๐๐๐
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google โค๏ธ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from packages.