-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
deps: set @types/node to >= #1575
Merged
alexander-fenster
merged 4 commits into
protobufjs:master
from
indutny:fix/set-types-node-to-star
Apr 14, 2021
Merged
deps: set @types/node to >= #1575
alexander-fenster
merged 4 commits into
protobufjs:master
from
indutny:fix/set-types-node-to-star
Apr 14, 2021
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When using `protobuf.js` as a dependency in a project it is important that `@types/node` package gets de-duped and has the same version as for the rest of the modules in the project. Otherwise, typing conflicts could happen as they do between v13 and v14 node types.
I'm happy with changing it to 14 as well, but I think |
We discussed it and we think it might be a little bit more permissive than needed, would it be OK if we make it |
Totally! This sounds great!
…On Fri, Apr 9, 2021 at 15:49 Alexander Fenster ***@***.***> wrote:
We discussed it and we think it might be a little bit more permissive than
needed, would it be OK if we make it >=13.7.0 instead? We can surely make
a release with this change if needed.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1575 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAB2HQYBUYZYN7EDVDPXVKDTH577VANCNFSM42JHJONA>
.
|
alexander-fenster
approved these changes
Apr 14, 2021
alexander-fenster
changed the title
deps: set @types/node to star version
deps: set @types/node to >=
Apr 14, 2021
Awesome. Thanks a lot! |
alexander-fenster
added a commit
that referenced
this pull request
Apr 29, 2021
* deps: set @types/node to star version When using `protobuf.js` as a dependency in a project it is important that `@types/node` package gets de-duped and has the same version as for the rest of the modules in the project. Otherwise, typing conflicts could happen as they do between v13 and v14 node types. * fix: use @types/node >=13.7.0 * fix: use @types/node >=13.7.0 Co-authored-by: Alexander Fenster <fenster@google.com> Co-authored-by: Alexander Fenster <github@fenster.name>
Closed
alexander-fenster
added a commit
that referenced
this pull request
Jul 7, 2022
* feat: proto3 optional support * chore: pre-release v6.11.0-pre * fix: rebuild * fix: fromObject should not initialize oneof members (#1597) * test: adding test for pbjs static code generation * fix: fromObject should not initialize oneof members * chore: release v6.11.0 * chore: rebuild * feat: add --no-service option for pbjs static target (#1577) This option skips generation of service clients. Co-authored-by: Alexander Fenster <fenster@google.com> * deps: set @types/node to >= (#1575) * deps: set @types/node to star version When using `protobuf.js` as a dependency in a project it is important that `@types/node` package gets de-duped and has the same version as for the rest of the modules in the project. Otherwise, typing conflicts could happen as they do between v13 and v14 node types. * fix: use @types/node >=13.7.0 * fix: use @types/node >=13.7.0 Co-authored-by: Alexander Fenster <fenster@google.com> Co-authored-by: Alexander Fenster <github@fenster.name> * chore: rebuild * docs: update changelog * fix: parse.js "parent.add(oneof)“ error (#1602) Co-authored-by: xiaoweili <xiaoweili@tencent.com> * chore: release v6.11.1 * fix(types): bring back Field.rule to .d.ts * fix: rebuild type, release v6.11.2 * build: configure backports * build: configure 6.x as default branch * fix: do not let setProperty change the prototype (#1731) * fix(deps): use eslint 8.x (#1728) * build: run tests if ci label added (#1734) * build: publish to main * chore(6.x): release 6.11.3 (#1737) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Support parsing of complex options * Use readValue to read the proto value and add better example * Fix lint issues * fix: rollback files * Re-do parse logic to take arrays into account and make it simpler Co-authored-by: Alexander Fenster <fenster@google.com> Co-authored-by: Matthew Douglass <5410142+mdouglass@users.noreply.github.com> Co-authored-by: Fedor Indutny <fedor.indutny@gmail.com> Co-authored-by: Alexander Fenster <github@fenster.name> Co-authored-by: leon <leon776@users.noreply.github.com> Co-authored-by: xiaoweili <xiaoweili@tencent.com> Co-authored-by: Benjamin Coe <bencoe@google.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using
protobuf.js
as a dependency in a project it is importantthat
@types/node
package gets de-duped and has the same version as forthe rest of the modules in the project. Otherwise, typing conflicts
could happen as they do between v13 and v14 node types.