-
Notifications
You must be signed in to change notification settings - Fork 613
Issues: microsoft/rushstack
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
[rush] Add option to minor bump package when a re-exported dependency minor bumps
#1063
opened Feb 1, 2019 by
ecraig12345
[api-extractor] Ability to ignore unsupported TypeScript constructs, rather than failing
enhancement
The issue is asking for a new feature or design change
#1046
opened Jan 21, 2019 by
shlomiassaf
[rush] Integrate git hooks to rush change when git push
general discussion
Not a bug or enhancement, just a discussion
#1042
opened Jan 19, 2019 by
lijunle
[rush] Support "unlinking" packages in a single repo so they do not automatically have versions bumped together on "rush version --bump" (or publish)
rush-publish-requirements
This issue describes user requirements that we should consider in the new design for "rush publish"
#1035
opened Jan 17, 2019 by
rlandav
[rush] How to use with React Native?
general discussion
Not a bug or enhancement, just a discussion
#1025
opened Jan 12, 2019 by
joerneu
[rush] Example does not build with yarn
bug
Something isn't working as intended
effort: easy
Probably a quick fix. Want to contribute? :-)
help wanted
If you're looking to contribute, this issue is a good place to start!
#1024
opened Jan 12, 2019 by
joerneu
[rush] "rush add" does not install package with npm
needs more info
We can't proceed because we need a better repro or an answer to a question
#1013
opened Jan 9, 2019 by
cortopy
[api-extractor] Generate declaration files in-memory as part of extraction
enhancement
The issue is asking for a new feature or design change
help wanted
If you're looking to contribute, this issue is a good place to start!
needs design
The next step is for someone to propose the details of an approach for solving the problem
#1010
opened Dec 30, 2018 by
yacinehmito
[rush] Give feedback when users haven't recently run Probably a quick fix. Want to contribute? :-)
enhancement
The issue is asking for a new feature or design change
help wanted
If you're looking to contribute, this issue is a good place to start!
rush install
effort: easy
#1004
opened Dec 20, 2018 by
christiango
[rush] Feature request: individual shrinkwrap / lockfile per project
enhancement
The issue is asking for a new feature or design change
#978
opened Dec 3, 2018 by
elliottsj
[api-extractor] Allow separate release tags for merged declarations
enhancement
The issue is asking for a new feature or design change
needs design
The next step is for someone to propose the details of an approach for solving the problem
#972
opened Nov 30, 2018 by
nvh
[rush] Warn if shouldPublish and versionPolicy are both set for a project
effort: easy
Probably a quick fix. Want to contribute? :-)
enhancement
The issue is asking for a new feature or design change
help wanted
If you're looking to contribute, this issue is a good place to start!
rush-publish-requirements
This issue describes user requirements that we should consider in the new design for "rush publish"
#958
opened Nov 26, 2018 by
ecraig12345
[api-extractor] Namespace-level objects getting dropped
enhancement
The issue is asking for a new feature or design change
needs more info
We can't proceed because we need a better repro or an answer to a question
priority
The maintainers consider it to be an important issue. We should try to fix it soon.
repro confirmed
The issue comments included repro instructions, and the maintainers reproduced the problem
#946
opened Nov 15, 2018 by
AlexJerabek
[rush] Independent shrinkwrap files for global commands
enhancement
The issue is asking for a new feature or design change
needs design
The next step is for someone to propose the details of an approach for solving the problem
#939
opened Nov 7, 2018 by
nickpape
[api-extractor] Module resolution extension point
needs more info
We can't proceed because we need a better repro or an answer to a question
#933
opened Nov 6, 2018 by
aeulitz
[rush] Don't autoretry 'rush update' (which nukes node_modules) when it won't help
effort: easy
Probably a quick fix. Want to contribute? :-)
enhancement
The issue is asking for a new feature or design change
help wanted
If you're looking to contribute, this issue is a good place to start!
#923
opened Nov 1, 2018 by
KRyan
[rush] All Something isn't working as intended
effort: easy
Probably a quick fix. Want to contribute? :-)
help wanted
If you're looking to contribute, this issue is a good place to start!
node_modules/.bin
point to the common .bin which precludes different packages with different bin versions
bug
#915
opened Oct 29, 2018 by
giltayar
[api-extractor] First-class support for per-field version/requirement set
enhancement
The issue is asking for a new feature or design change
needs more info
We can't proceed because we need a better repro or an answer to a question
#906
opened Oct 26, 2018 by
AlexJerabek
[rush] Let's make publishing easier and more flexible
enhancement
The issue is asking for a new feature or design change
needs design
The next step is for someone to propose the details of an approach for solving the problem
rush-publish-requirements
This issue describes user requirements that we should consider in the new design for "rush publish"
#904
opened Oct 25, 2018 by
octogonz
[rush] publish -a has confusing documentation
rush-publish-requirements
This issue describes user requirements that we should consider in the new design for "rush publish"
#900
opened Oct 24, 2018 by
Sushisource
[api-extractor] Option to extend analysis beyond package boundaries
enhancement
The issue is asking for a new feature or design change
needs design
The next step is for someone to propose the details of an approach for solving the problem
#896
opened Oct 22, 2018 by
aeulitz
[rush] Let's get NPM 6 working with Rush
general discussion
Not a bug or enhancement, just a discussion
#886
opened Oct 17, 2018 by
octogonz
[rush] Generate a change file for projects that don't publish via npm
enhancement
The issue is asking for a new feature or design change
needs design
The next step is for someone to propose the details of an approach for solving the problem
rush-publish-requirements
This issue describes user requirements that we should consider in the new design for "rush publish"
#884
opened Oct 17, 2018 by
factoidforrest
[api-documenter] Function overloads sometimes are displayed with the same name
ae-ambiguous-ids
This issue belongs to a set of bugs tracked by Pete
bug
Something isn't working as intended
#881
opened Oct 16, 2018 by
AlexJerabek
ProTip!
Type g i on any issue or pull request to go back to the issue listing page.