Title: [Feat]: Align the dependencies for binary and NPM artifact releases · Issue #4927 · coder/code-server · GitHub
Open Graph Title: [Feat]: Align the dependencies for binary and NPM artifact releases · Issue #4927 · coder/code-server
X Title: [Feat]: Align the dependencies for binary and NPM artifact releases · Issue #4927 · coder/code-server
Description: This issue is to continue the discussion from #4918 regarding the different release methods of code-server, and how NPM artifacts work. What is your suggestion? Be in a state where the builds and installs are both deterministic when it c...
Open Graph Description: This issue is to continue the discussion from #4918 regarding the different release methods of code-server, and how NPM artifacts work. What is your suggestion? Be in a state where the builds and i...
X Description: This issue is to continue the discussion from #4918 regarding the different release methods of code-server, and how NPM artifacts work. What is your suggestion? Be in a state where the builds and i...
Opengraph URL: https://github.com/coder/code-server/issues/4927
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[Feat]: Align the dependencies for binary and NPM artifact releases","articleBody":"This issue is to continue the discussion from #4918 regarding the different release methods of code-server, and how NPM artifacts work.\r\n\r\n## What is your suggestion?\r\n* Be in a state where the builds and installs are both deterministic when it comes to dependencies.\r\n* Avoid having the dependencies being figured out at install time of the NPM package.\r\n\r\n\r\n## Why do you want this feature?\r\nRight now, there's inconsistency on what dependencies might get used for the binaries generated (because they get generated after installing and building the package - which is an action that does respect the `yarn.lock` file) and the NPM artifacts (because the lockfiles are not published, nor the lockfiles for dependencies gets respected even if published).\r\n\r\nThis causes problems of dependency drifts like what was seen in #4900 - where releases might use different versions or worse, something working on release stops working because of newer versions being published.\r\n\r\n## Are there any workarounds to get this functionality today?\r\nNot for the end-user. Specific versions can be pinned under the `package.json` file in this repo, but not something controlled by the end-user.\r\n\r\n## Are you interested in submitting a PR for this?\r\nYes","author":{"url":"https://github.com/edvincent","@type":"Person","name":"edvincent"},"datePublished":"2022-03-01T03:18:06Z","url":"https://github.com/coder/code-server/issues/4927"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:1799dba2-4ad1-0a31-7e8d-8cbf5e7ba61a |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | DDF0:96DDF:30EAC66:3E10E2C:6B01C288 |
| html-safe-nonce | 604d34e00df52a8315ea63e011fc3846e997c9c8956063edc99be72d4017b0fe |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJEREYwOjk2RERGOjMwRUFDNjY6M0UxMEUyQzo2QjAxQzI4OCIsInZpc2l0b3JfaWQiOiIzMTMzMTEwNjAzMzU1Mzc0MjE2IiwicmVnaW9uX2VkZ2UiOiJpYWQiLCJyZWdpb25fcmVuZGVyIjoiaWFkIn0= |
| visitor-hmac | c219ecdfd58f3f68d83c9df21618ab8d589d8f06f4bc5be2af71da50f7840fd4 |
| hovercard-subject-tag | issue:1154809177 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/coder/code-server/4927/issue_layout |
| twitter:image | https://opengraph.githubassets.com/164a32af6fa0785edf69dc5a87238cc77078afb6422fe258249b4a3941870abc/coder/code-server/issues/4927 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/164a32af6fa0785edf69dc5a87238cc77078afb6422fe258249b4a3941870abc/coder/code-server/issues/4927 |
| og:image:alt | This issue is to continue the discussion from #4918 regarding the different release methods of code-server, and how NPM artifacts work. What is your suggestion? Be in a state where the builds and i... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | edvincent |
| hostname | github.com |
| expected-hostname | github.com |
| None | cc5dfdd32f62ebd3223cab3af3aa2b268d3605218237326a48a99d1efd89495c |
| turbo-cache-control | no-preview |
| go-import | github.com/coder/code-server git https://github.com/coder/code-server.git |
| octolytics-dimension-user_id | 95932066 |
| octolytics-dimension-user_login | coder |
| octolytics-dimension-repository_id | 172953845 |
| octolytics-dimension-repository_nwo | coder/code-server |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 172953845 |
| octolytics-dimension-repository_network_root_nwo | coder/code-server |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 8c77c9e8439031ad54c75a250694842892f693e1 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width