NR1 Top allows you to display and inspect the top processes of your hosts, including CPU, I/O and memory.
Home Page: https://github.com/newrelic/nr1-top/discussions
License: Apache License 2.0
I followed the steps provided for installation and am able to get the app built, published, deployed and subscribed to.
I have followed the same method for other apps and they do display from local server and when published. (e.g. nr1-groundskeeper, nr1-container-explorer, nr1-neon)
OUTPUT: nr1 nerdpack:info --verbose
init version: @oclif/[email protected] argv: [ '--verbose', [length]: 1 ]
Fetching info from registry...
Request: POST https://artifact-registry.service.newrelic.com/graphql
Data: 'query {\n package(uuid: ' +
'"f4147f2d-7c86-47d6-98df-b7a15cf00a85") {\n ' +
' uuid\n accountId\n ' +
' publications {\n createdAt\n ' +
' createdByUser\n ' +
'version\n }\n }\n ' +
' packageDeployments(uuid: ' +
'"f4147f2d-7c86-47d6-98df-b7a15cf00a85") {\n ' +
' channel\n deployedPublication {\n ' +
' version\n }\n ' +
' }\n }'
Headers: {
'API-Key': '',
'Content-Type': 'application/graphql'
}
Registry: Present
Id: f4147f2d-7c86-47d6-98df-b7a15cf00a85
Region: us
Account ID: 1847652
Local version: 0.1.5
Version Date Deployed to channel
0.1.5 14 minutes ago DEV
LOCAL SERVER EXECUTION
STEP: Install
npm install
STEP: Run locally
npm start
STEP: Test
https://one.newrelic.com/?nerdpacks=local
PUBLISH TO NEW RELIC ONE
STEP: Create a new UUID
nr1 nerdpack:uuid -gf
Generated id is f4147f2d-7c86-47d6-98df-b7a15cf00a85
STEP: Force publish, override version if exists
nr1 nerdpack:publish -f
STEP: Deploy to DEV
nr1 nerdpack:deploy --channel=DEV
STEP: Subscribe to DEV
nr1 nerdpack:subscribe --channel=DEV
STEP: Check info
nr1 nerdpack:info --verbose
Version Date Deployed to channel
0.1.5 4 minutes ago DEV
What additional information should I provide to help with troubleshooting?
Would it be possible to show the full commands that are listed in the "Command" column?
We use a lot of different parameters in our environment, and it would help if we could view the full command the process is using.
Update chart styling to more closely match the rest of New Relic
The current implementation on those components falls outside of our best practice. We need to resolve that.
Top is currently configured to use old eslint and prettier standards defined in package.json. This needs to be updated to utilize @newrelic/eslint-plugin-newrelic, which will also require reformatting all existing code. This should all be completed as a single effort.
Should remove these existing devDependencies:
"babel-eslint": "^10.0.3",
"eslint-config-prettier": "^6.2.0",
"eslint-plugin-prettier": "^3.1.0",
"eslint-plugin-react": "^7.14.3",
And add this one:
"@newrelic/eslint-plugin-newrelic": "^0.3.0"
Should also update .eslintrc.js to comply with:
https://github.com/newrelic/open-source-tools/blob/master/nerdpacks/oss-template/.eslintrc.js
🤖This issue was automatically generated by repolinter-action, developed by the Open Source and Developer Advocacy team at New Relic. This issue will be automatically updated or closed when changes are pushed. If you have any problems with this tool, please feel free to open a GitHub issue or give us a ping in #help-opensource.
This Repolinter run generated the following results:
| ❗ Error | ❌ Fail | ✅ Pass | Ignored | Total | |
|---|---|---|---|---|---|
| 0 | 1 | 0 | 12 | 0 | 13 |
license-file-existsreadme-file-existsreadme-starts-with-nr1-catalog-headerreadme-contains-security-sectionreadme-contains-link-to-security-policyreadme-contains-discuss-topicthird-party-notices-file-existsgithub-actions-workflow-file-existsnr1-catalog-config-file-existsnr1-catalog-screenshots-directory-existsnr1-catalog-documentation-file-existspackage-scripts-presentcode-of-conduct-should-not-exist-here #New Relic has moved the CODE_OF_CONDUCT file to a centralized location where it is referenced automatically by every repository in the New Relic organization. Because of this change, any other CODE_OF_CONDUCT file in a repository is now redundant and should be removed. For more information please visit https://docs.google.com/document/d/1y644Pwi82kasNP5VPVjDV8rsmkBKclQVHFkz8pwRUtE/view. Found files. Below is a list of files or patterns that failed:
CODE_OF_CONDUCT.md
license-file-exists #Found file (LICENSE). New Relic requires that all open source projects have an associated license contained within the project. This license must be permissive (e.g. non-viral or copyleft), and we recommend Apache 2.0 for most use cases. For more information please visit https://docs.google.com/document/d/1vML4aY_czsY0URu2yiP3xLAKYufNrKsc7o4kjuegpDw/edit.
readme-file-exists #Found file (README.md). New Relic requires a README file in all projects. This README should give a general overview of the project, and should point to additional resources (security, contributing, etc.) where developers and users can learn further. For more information please visit https://github.com/newrelic/open-source-tools/tree/master/javascript/oss-template.
readme-starts-with-nr1-catalog-header #The first 1 lines contain all of the requested patterns. (README.md). The README of a community plus project should have a NR1 Catalog header at the start of the README. If you already have a NR1 Catalog header and this rule is failing, your header may be out of date, and you should update your header with the suggested one below. For more information please visit https://opensource.newrelic.com/oss-category/.
readme-contains-security-section #Contains a security section (README.md). New Relic recommends having a Security section in your README to address concerns such as vulnerability reporting. This security section should also contain a link to the security policy (found under the "Security" tab of the repository). For an example of this section, please see the NR1 Catalog Template. For more information please visit https://nerdlife.datanerd.us/new-relic/security-guidelines-for-publishing-source-code.
readme-contains-link-to-security-policy #Contains a link to the security policy for this repository (README.md). New Relic recommends referencing the open source security policy (https://github.com/newrelic/<repo-name>/security/policy or ../../security/policy) in a Security section in the README. For an example of this, please see the NR1 Catalog Template. For more information please visit https://nerdlife.datanerd.us/new-relic/security-guidelines-for-publishing-source-code.
readme-contains-discuss-topic #Contains a link to the appropriate discuss.newrelic.com topic (README.md). New Relic recommends directly linking the your appropriate discuss.newrelic.com topic in the README, allowing developer an alternate method of getting support. For more information please visit https://nerdlife.datanerd.us/new-relic/security-guidelines-for-publishing-source-code.
third-party-notices-file-exists #Found file (THIRD_PARTY_NOTICES.md). A THIRD_PARTY_NOTICES.md file must be present to grant attribution to all dependencies being used by this project. For JavaScript projects, you can generate this file using the oss-cli. For more information please visit https://docs.google.com/document/d/1y644Pwi82kasNP5VPVjDV8rsmkBKclQVHFkz8pwRUtE/view.
github-actions-workflow-file-exists #Found file (.github/workflows/catalog.yml). Any Community Plus project must integrate with GitHub actions. For more information please visit https://docs.google.com/document/d/1y644Pwi82kasNP5VPVjDV8rsmkBKclQVHFkz8pwRUtE/view.
nr1-catalog-config-file-exists #Found file (catalog/config.json).
nr1-catalog-screenshots-directory-exists #Found file (catalog/screenshots).
nr1-catalog-documentation-file-exists #Found file (catalog/documentation.md).
package-scripts-present #An eslint-check and eslint-fix npm script found in file (package.json). NPM scripts for ESLint (eslint-check and eslint-fix) are required to properly integrate with the nerdpack system.
🤖This issue was automatically generated by repolinter-action, developed by the Open Source and Developer Advocacy team at New Relic. This issue will be automatically updated or closed when changes are pushed. If you have any problems with this tool, please feel free to open a GitHub issue or give us a ping in #help-opensource.
This Repolinter run generated the following results:
| ❗ Error | ❌ Fail | ✅ Pass | Ignored | Total | |
|---|---|---|---|---|---|
| 0 | 2 | 0 | 11 | 0 | 13 |
license-file-existsreadme-file-existsreadme-contains-security-sectionreadme-contains-link-to-security-policythird-party-notices-file-existscode-of-conduct-should-not-exist-heregithub-actions-workflow-file-existsnr1-catalog-config-file-existsnr1-catalog-screenshots-directory-existsnr1-catalog-documentation-file-existspackage-scripts-presentreadme-starts-with-nr1-catalog-header #The README of a community plus project should have a NR1 Catalog header at the start of the README. If you already have a NR1 Catalog header and this rule is failing, your header may be out of date, and you should update your header with the suggested one below. For more information please visit https://opensource.newrelic.com/oss-category/. Below is a list of files or patterns that failed:
README.md: The first 1 lines do not contain the pattern(s): Open source NR1 Catalog header (see https://opensource.newrelic.com/oss-category).
the latest code snippet found at https://github.com/newrelic/opensource-website/wiki/Open-Source-Category-Snippets#code-snippet-3 to filereadme-contains-forum-topic #Doesn't contain a link to the appropriate forum.newrelic.com topic (README.md). New Relic recommends directly linking the your appropriate forum.newrelic.com topic in the README, allowing developer an alternate method of getting support. For more information please visit https://nerdlife.datanerd.us/new-relic/security-guidelines-for-publishing-source-code.
license-file-exists #Found file (LICENSE). New Relic requires that all open source projects have an associated license contained within the project. This license must be permissive (e.g. non-viral or copyleft), and we recommend Apache 2.0 for most use cases. For more information please visit https://docs.google.com/document/d/1vML4aY_czsY0URu2yiP3xLAKYufNrKsc7o4kjuegpDw/edit.
readme-file-exists #Found file (README.md). New Relic requires a README file in all projects. This README should give a general overview of the project, and should point to additional resources (security, contributing, etc.) where developers and users can learn further. For more information please visit https://github.com/newrelic/open-source-tools/tree/master/javascript/oss-template.
readme-contains-security-section #Contains a security section (README.md). New Relic recommends having a Security section in your README to address concerns such as vulnerability reporting. This security section should also contain a link to the security policy (found under the "Security" tab of the repository). For an example of this section, please see the NR1 Catalog Template. For more information please visit https://nerdlife.datanerd.us/new-relic/security-guidelines-for-publishing-source-code.
readme-contains-link-to-security-policy #Contains a link to the security policy for this repository (README.md). New Relic recommends referencing the open source security policy (https://github.com/newrelic/<repo-name>/security/policy or ../../security/policy) in a Security section in the README. For an example of this, please see the NR1 Catalog Template. For more information please visit https://nerdlife.datanerd.us/new-relic/security-guidelines-for-publishing-source-code.
third-party-notices-file-exists #Found file (THIRD_PARTY_NOTICES.md). A THIRD_PARTY_NOTICES.md file must be present to grant attribution to all dependencies being used by this project. For JavaScript projects, you can generate this file using the oss-cli. For more information please visit https://docs.google.com/document/d/1y644Pwi82kasNP5VPVjDV8rsmkBKclQVHFkz8pwRUtE/view.
code-of-conduct-should-not-exist-here #New Relic has moved the CODE_OF_CONDUCT file to a centralized location where it is referenced automatically by every repository in the New Relic organization. Because of this change, any other CODE_OF_CONDUCT file in a repository is now redundant and should be removed. For more information please visit https://docs.google.com/document/d/1y644Pwi82kasNP5VPVjDV8rsmkBKclQVHFkz8pwRUtE/view. Did not find a file matching the specified patterns. All files passed this test.
github-actions-workflow-file-exists #Found file (.github/workflows/catalog.yml). Any Community Plus project must integrate with GitHub actions. For more information please visit https://docs.google.com/document/d/1y644Pwi82kasNP5VPVjDV8rsmkBKclQVHFkz8pwRUtE/view.
nr1-catalog-config-file-exists #Found file (catalog/config.json).
nr1-catalog-screenshots-directory-exists #Found file (catalog/screenshots).
nr1-catalog-documentation-file-exists #Found file (catalog/documentation.md).
package-scripts-present #An eslint-check and eslint-fix npm script found in file (package.json). NPM scripts for ESLint (eslint-check and eslint-fix) are required to properly integrate with the nerdpack system.
It would be nice if the process list could scroll independent of the charts on the right pane. When a user scrolls down to the bottom of the process list, and clicks on a process towards the bottom of the list, they have to scroll back up to see the the charts on the top.
Add metadata to the repository that matches the example laid out here.
config.json file to a catalog directory in the repo root, matching this format./screenshots directory into catalog:
README.md.README.md.documentation.md to be absolute pathsadditionalInfo.md file to a catalog directory in the repo root, matching this format.README.md commands section matches Justin's snippet.npm start and let the CLI move the nr1.json
rm -r node_modules
npm uninstall eslint
npm install --save-dev eslint
When you select a custom time range, the interface crashes.
Respecting the time range
N/A
Top is using a custom styled table - update to use the standard NR table component for visual consistency.
Let the chart Y axis determine “M”, “G”, etc. Otherwise you get “2K MB” for 2GB.
Empty state is blank. Implement the nr1-community component
The version in the package.json should match up to what's in the package-lock.json
Might need to modify semantic-release-bot so it updates package-lock.json appropriately.
This report was generated automatically by the Repolinter.
This Repolinter run generated the following results:
| ❗ Error | ❌ Fail | ✅ Pass | Ignored | Total | |
|---|---|---|---|---|---|
| 0 | 0 | 0 | 7 | 0 | 7 |
nr1-lib-deprecation-dropdown-labelnr1-lib-deprecation-accountpicker-onchangenr1-lib-deprecation-icon-sizetypenr1-lib-deprecation-entity-title-table-row-cell-value-reportingnr1-lib-deprecation-tooltip-classnamenr1-lib-deprecation-tooltip-stylenr1-lib-deprecation-tablerow-actions-icontypenr1-lib-deprecation-dropdown-label #See the New Relic Developer docs for current API details https://developer.newrelic.com/components/dropdown. For more information please visit newrelic/developer-website#1033. All files passed this test.
nr1-lib-deprecation-accountpicker-onchange #See the New Relic Developer docs for current API details https://developer.newrelic.com/components/account-picker. For more information please visit newrelic/developer-website#1033. All files passed this test.
nr1-lib-deprecation-icon-sizetype #See the New Relic Developer docs for current API details https://developer.newrelic.com/components/icon. For more information please visit newrelic/developer-website#1033. All files passed this test.
nr1-lib-deprecation-entity-title-table-row-cell-value-reporting #See the New Relic Developer docs for current API details https://developer.newrelic.com/components/entity-title-table-row-cell. For more information please visit newrelic/developer-website#1033. All files passed this test.
nr1-lib-deprecation-tooltip-classname #See the New Relic Developer docs for current API details https://developer.newrelic.com/components/tooltip. For more information please visit newrelic/developer-website#1033. All files passed this test.
nr1-lib-deprecation-tooltip-style #See the New Relic Developer docs for current API details https://developer.newrelic.com/components/tooltip. For more information please visit newrelic/developer-website#1033. All files passed this test.
nr1-lib-deprecation-tablerow-actions-icontype #See the New Relic Developer docs for current API details https://developer.newrelic.com/components/table-row. For more information please visit newrelic/developer-website#1033. All files passed this test.
🤖This issue was automatically generated by repolinter-action, developed by the Open Source and Developer Advocacy team at New Relic. This issue will be automatically updated or closed when changes are pushed. If you have any problems with this tool, please feel free to open a GitHub issue or give us a ping in #help-opensource.
This Repolinter run generated the following results:
| ❗ Error | ❌ Fail | ✅ Pass | Ignored | Total | |
|---|---|---|---|---|---|
| 0 | 0 | 0 | 13 | 0 | 13 |
license-file-existsreadme-file-existsreadme-starts-with-nr1-catalog-headerreadme-contains-security-sectionreadme-contains-link-to-security-policyreadme-contains-discuss-topicthird-party-notices-file-existscode-of-conduct-should-not-exist-heregithub-actions-workflow-file-existsnr1-catalog-config-file-existsnr1-catalog-screenshots-directory-existsnr1-catalog-documentation-file-existspackage-scripts-presentlicense-file-exists #Found file (LICENSE). New Relic requires that all open source projects have an associated license contained within the project. This license must be permissive (e.g. non-viral or copyleft), and we recommend Apache 2.0 for most use cases. For more information please visit https://docs.google.com/document/d/1vML4aY_czsY0URu2yiP3xLAKYufNrKsc7o4kjuegpDw/edit.
readme-file-exists #Found file (README.md). New Relic requires a README file in all projects. This README should give a general overview of the project, and should point to additional resources (security, contributing, etc.) where developers and users can learn further. For more information please visit https://github.com/newrelic/open-source-tools/tree/master/javascript/oss-template.
readme-starts-with-nr1-catalog-header #The first 1 lines contain all of the requested patterns. (README.md). The README of a community plus project should have a NR1 Catalog header at the start of the README. If you already have a NR1 Catalog header and this rule is failing, your header may be out of date, and you should update your header with the suggested one below. For more information please visit https://opensource.newrelic.com/oss-category/.
readme-contains-security-section #Contains a security section (README.md). New Relic recommends having a Security section in your README to address concerns such as vulnerability reporting. This security section should also contain a link to the security policy (found under the "Security" tab of the repository). For an example of this section, please see the NR1 Catalog Template. For more information please visit https://nerdlife.datanerd.us/new-relic/security-guidelines-for-publishing-source-code.
readme-contains-link-to-security-policy #Contains a link to the security policy for this repository (README.md). New Relic recommends referencing the open source security policy (https://github.com/newrelic/<repo-name>/security/policy or ../../security/policy) in a Security section in the README. For an example of this, please see the NR1 Catalog Template. For more information please visit https://nerdlife.datanerd.us/new-relic/security-guidelines-for-publishing-source-code.
readme-contains-discuss-topic #Contains a link to the appropriate discuss.newrelic.com topic (README.md). New Relic recommends directly linking the your appropriate discuss.newrelic.com topic in the README, allowing developer an alternate method of getting support. For more information please visit https://nerdlife.datanerd.us/new-relic/security-guidelines-for-publishing-source-code.
third-party-notices-file-exists #Found file (THIRD_PARTY_NOTICES.md). A THIRD_PARTY_NOTICES.md file must be present to grant attribution to all dependencies being used by this project. For JavaScript projects, you can generate this file using the oss-cli. For more information please visit https://docs.google.com/document/d/1y644Pwi82kasNP5VPVjDV8rsmkBKclQVHFkz8pwRUtE/view.
code-of-conduct-should-not-exist-here #New Relic has moved the CODE_OF_CONDUCT file to a centralized location where it is referenced automatically by every repository in the New Relic organization. Because of this change, any other CODE_OF_CONDUCT file in a repository is now redundant and should be removed. For more information please visit https://docs.google.com/document/d/1y644Pwi82kasNP5VPVjDV8rsmkBKclQVHFkz8pwRUtE/view. Did not find a file matching the specified patterns. All files passed this test.
github-actions-workflow-file-exists #Found file (.github/workflows/catalog.yml). Any Community Plus project must integrate with GitHub actions. For more information please visit https://docs.google.com/document/d/1y644Pwi82kasNP5VPVjDV8rsmkBKclQVHFkz8pwRUtE/view.
nr1-catalog-config-file-exists #Found file (catalog/config.json).
nr1-catalog-screenshots-directory-exists #Found file (catalog/screenshots).
nr1-catalog-documentation-file-exists #Found file (catalog/documentation.md).
package-scripts-present #An eslint-check and eslint-fix npm script found in file (package.json). NPM scripts for ESLint (eslint-check and eslint-fix) are required to properly integrate with the nerdpack system.
Regardless if I serve this up locally or publish/deploy/subscribe, this Nerdpack does not show up in New Relic One.
Update text elements (e.g. heading, paragraph) to use the relevant NR component instead
🤖This issue was automatically generated by repolinter-action, developed by the Open Source and Developer Advocacy team at New Relic. This issue will be automatically updated or closed when changes are pushed. If you have any problems with this tool, please feel free to open a GitHub issue or give us a ping in #help-opensource.
This Repolinter run generated the following results:
| ❗ Error | ❌ Fail | ✅ Pass | Ignored | Total | |
|---|---|---|---|---|---|
| 0 | 3 | 0 | 9 | 0 | 12 |
readme-starts-with-nr1-catalog-header #The README of a community plus project should have a NR1 Catalog header at the start of the README. If you already have a NR1 Catalog header and this rule is failing, your header may be out of date. For more information please visit https://opensource.newrelic.com/oss-category/. Below is a list of files or patterns that failed:
README.md: The first 1 lines do not contain the pattern(s): Open source NR1 Catalog header (see https://opensource.newrelic.com/oss-category).
[](https://opensource.newrelic.com/oss-category/#new-relic-one-catalog-project) to filereadme-contains-security-section #Doesn't contain a security section (README.md). New Relic recommends having a Security section in your README to address concerns such as vulnerability reporting. This security section should also contain a link to the security policy (found under the "Security" tab of the repository). For an example of this section, please see the NR1 Catalog Template. For more information please visit https://nerdlife.datanerd.us/new-relic/security-guidelines-for-publishing-source-code.
readme-contains-link-to-security-policy #Doesn't contain a link to the security policy for this repository (README.md). New Relic recommends referencing the open source security policy (https://github.com/newrelic/<repo-name>/security/policy) in a Security section in the README. For an example of this, please see the NR1 Catalog Template. For more information please visit https://nerdlife.datanerd.us/new-relic/security-guidelines-for-publishing-source-code.
license-file-exists #Found file (LICENSE). New Relic requires that all open source projects have an associated license contained within the project. This license must be permissive (e.g. non-viral or copyleft), and we recommend Apache 2.0 for most use cases. For more information please visit https://docs.google.com/document/d/1vML4aY_czsY0URu2yiP3xLAKYufNrKsc7o4kjuegpDw/edit.
readme-file-exists #Found file (README.md). New Relic requires a README file in all projects. This README should give a general overview of the project, and should point to additional resources (security, contributing, etc.) where developers and users can learn further. For more information please visit https://github.com/newrelic/open-source-tools/tree/master/javascript/oss-template.
readme-contains-discuss-topic #Contains a link to the appropriate discuss.newrelic.com topic (README.md). New Relic recommends directly linking the your appropriate discuss.newrelic.com topic in the README, allowing developer an alternate method of getting support. For more information please visit https://nerdlife.datanerd.us/new-relic/security-guidelines-for-publishing-source-code.
third-party-notices-file-exists #Found file (THIRD_PARTY_NOTICES.md). A THIRD_PARTY_NOTICES.md file must be present to grant attribution to all dependencies being used by this project. For JavaScript projects, you can generate this file using the oss-cli. For more information please visit https://docs.google.com/document/d/1y644Pwi82kasNP5VPVjDV8rsmkBKclQVHFkz8pwRUtE/view.
github-actions-workflow-file-exists #Found file (.github/workflows/pr.yml). Any Community Plus project must integrate with GitHub actions. For more information please visit https://docs.google.com/document/d/1y644Pwi82kasNP5VPVjDV8rsmkBKclQVHFkz8pwRUtE/view.
nr1-catalog-config-file-exists #Found file (catalog/config.json).
nr1-catalog-screenshots-directory-exists #Found file (catalog/screenshots).
nr1-catalog-documentation-file-exists #Found file (catalog/documentation.md).
package-scripts-present #An eslint-check and eslint-fix npm script found in file (package.json). NPM scripts for ESLint (eslint-check and eslint-fix) are required to properly integrate with the nerdpack system.
The content at the top of the right column <div class="summary-panel">...</div> disappears when you resize your browser window.
<div class="summary-panel">...</div> will disappearI expect that the summary panel would remain visible when I resize my window.
No relevant console output :/
May be related to #10, but I don't think it's the same. Likely a similar or the same cause, but different effect.
Hi
I just read the announcement about these NR1 apps and followed the instructions to successfully create a new app, start it, and see the placeholder for it in the New Relic One page.
I was also able to get this to work with the GraphQL sample app.
When I do the same for nr1-top, there are no problems with build or start, but there is no entry for "top" in New Relic One.
Grateful for any help, thanks.
Replace the EmptyState component imported from the NR1 community project w/ the standard NR1 StateComponent
Being able to sort columns on the top grid would be cool
The summary-panel renders inconsistently, when switching between processes. To be more specific, the panel renders on initial load, but then may not render at all when switching between processes
The summary-panel (top-right, which includes the commandName, commandLine and parent/child process id's) will occasionally not render when selecting a new process, or after re-selecting a process which had been previously selected and for which the panel previously rendered.
In NR1, locate a host, and load the Top nerdlet. Select a process other than the one currently selected at load, re-select the original process. The summary panel does not render.
In NR1, locate a host, and load the Top nerdlet. Select a process other than the one currently selected at load, then select another. After several selections, the summary panel no longer renders. Note, navigating using the child/parent link yields the same result.
The summary-panel should load consistently, for every process
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 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.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
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.