Comments (7)
this will immediately break on them as the dependencies will be bumped to the latest incompatible version.
Can you clarify how this scenario happens? If the dependent library is modified in a way that breaks the consuming library, the consuming library should be updated.
If you're talking about changes in language syntax, we plan to publish specific tagged versions (@ts2.0
, etc) that represent the latest version of the definition file that's compatible with that version of the compiler. Those versions won't use *
version numbers.
from types-publisher.
No, not changes in the language.
Say I'm relying on Express 4.x and @types/[email protected]
. There's just been a new release, @types/[email protected]
. Both these depend on @types/serve-static@*
. If @types/serve-static
gets updated, anyone using older @types/express
versions are now broken as the dependencies are not pinned to a version.
from types-publisher.
Or the even more basic use-case, the typings themselves were incorrect for 1.2.5
, so we update them. However, they were used as a dependency somewhere. That update will break the build for anyone relying on the older typings since they aren't pinned.
from types-publisher.
What do you think the right behavior is?
from types-publisher.
The way I worked with this was by always pinning. However, that means you in the current system you'll have to track changes of a dependency to update a new version and that'll could be trickier. Perhaps following a pattern like Typings were there's a manifest for dependencies?
from types-publisher.
I'm inclined to fix at e.g. 2.1.*
and rely on people to not make breaking changes in file updates without updating downstream consumers.
from types-publisher.
Makes sense, you'll just need to police things a little bit then - I believe there's been a few issues around changing signatures of a library when it really does make sense, but it will break consumers who don't have pinned versions. This is really the only part that may be at odds with using NPM, since NPM install by default with ^
while you probably want --save-exact
more. That said, changes happen and things can break even with a normal TypeScript module, I think it'll just rely on better policing for changes between patches and even minor versions (since ^
will install minors).
from types-publisher.
Related Issues (20)
- Please add vue-property-decorator to the whitelist HOT 7
- Please make `checkTypeScriptVersions` aggregate version mismatches
- Scoped & versioned packages can't pass path mappings checks
- Resurrect crawl-npm.ts
- Improve notNeededPackages.json testing HOT 1
- Update outdated packages HOT 1
- testDependencies should include only top-level package names HOT 1
- publish-registry validation fails when new packages are out but we won't publish them for a week
- Changes published from DefinitelyTyped are not marked as 'latest' HOT 1
- 'download' is not allowed in new npm package names
- Can't unpublish fastify-static HOT 2
- Deprecated packages often fail to publish correctly
- types-publisher is crashing during indexing HOT 3
- Optional catch binding in util.ts is failing PRs on DefinitelyTyped
- Error running tests (Error: Unexpected path .DS_Store) HOT 1
- index.d.ts should be the only d.ts file allowed in tsconfig.json HOT 10
- Tests do not run reliably on Windows
- getLatestMatch throws "Could not find version [object Object]"
- Dependencies information in NPM registry saved with "^[object Object]" value HOT 1
- typesVersions gets mangled in the published package 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 types-publisher.