Uh oh!
There was an error while loading. Please reload this page.
chore: remove performance section of ES6 page - #3181
Merged
Conversation
Trott
commented
May 19, 2020
MemberAuthor
@alexandrtovmach Am I doing this right? Or do these changes need to go through Crowdin somehow? |
Trott
commented
May 19, 2020
MemberAuthor
|
Trott
commented
May 20, 2020
MemberAuthor
@nodejs/website |
nschonni
approved these changes
May 20, 2020
nschonni
left a comment
Member
There was a problem hiding this comment.
Not sure if the ro and fr pages should just be removed since they appear to be only English
Information linked is out of date. Including an ES6 page is probably something that needs to be re-thought entirely. Fixes: #3176
3imed-jaberi
approved these changes
May 20, 2020
XhmikosR
approved these changes
May 20, 2020
This file contains hidden or 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
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
Information linked is out of date. Including an ES6 page is probably
something that needs to be re-thought entirely.
Fixes: #3176
@fhinkel