Build fails with Internal Error: website@workspace:.: This package doesn't seem to be present in your lockfile;

My app at GitHub - adriatic/tandem: RWJS Community Guides and Blogs on testing and debugging fails in build stage with error message “Internal Error: website@workspace:.: This package doesn’t seem to be present in your lockfile; run “yarn install” to update the lockfile”.

It is set for continuous deployment. Note that the build stage on my development computer works just fine.

This problem with the same app did not show up yesterday

Help please !

To verify that the problem is in “build step” running on Netlify, I uploaded the build folder from my machine to netlify (using the manual deployment method):

Settings for storied-kulfi-1978ec
storied-kulfi-1978ec.netlify.app

Manual deploys. Owned by Nikolaj Ivancic's team.

Last update at 6:29 PM (3 hours ago)

As you can verify the app https://storied-kulfi-1978ec.netlify.app/ works just fine.

Lastly the command yarn info yields:

nik$ yarn info
├─ @docusaurus/core@npm:2.0.0-beta.18
│  ├─ Instances: 1
│  ├─ Version: 2.0.0-beta.18
│  │
│  ├─ Exported Binaries
│  │  └─ docusaurus
│  │
│  └─ Dependencies
│     ├─ @babel/core@npm:^7.17.8 → npm:7.17.8
│     ├─ @babel/generator@npm:^7.17.7 → npm:7.17.7
│     ├─ @babel/plugin-syntax-dynamic-import@npm:^7.8.3 → npm:7.8.3
│     ├─ @babel/plugin-transform-runtime@npm:^7.17.0 → npm:7.17.0
│     ├─ @babel/preset-env@npm:^7.16.11 → npm:7.16.11
│     ├─ @babel/preset-react@npm:^7.16.7 → npm:7.16.7
│     ├─ @babel/preset-typescript@npm:^7.16.7 → npm:7.16.7
│     ├─ @babel/runtime-corejs3@npm:^7.17.8 → npm:7.17.8
│     ├─ @babel/runtime@npm:^7.17.8 → npm:7.17.8
│     ├─ @babel/traverse@npm:^7.17.3 → npm:7.17.3
│     ├─ @docusaurus/cssnano-preset@npm:2.0.0-beta.18 → npm:2.0.0-beta.18
│     ├─ @docusaurus/logger@npm:2.0.0-beta.18 → npm:2.0.0-beta.18
│     ├─ @docusaurus/mdx-loader@npm:2.0.0-beta.18 → npm:2.0.0-beta.18
│     ├─ @docusaurus/react-loadable@npm:5.5.2 → npm:5.5.2
│     ├─ @docusaurus/utils-common@npm:2.0.0-beta.18 → npm:2.0.0-beta.18
│     ├─ @docusaurus/utils-validation@npm:2.0.0-beta.18 → npm:2.0.0-beta.18
│     ├─ @docusaurus/utils@npm:2.0.0-beta.18 → npm:2.0.0-beta.18
│     ├─ @slorber/static-site-generator-webpack-plugin@npm:^4.0.4 → npm:4.0.4
│     ├─ @svgr/webpack@npm:^6.2.1 → npm:6.2.1
│     ├─ autoprefixer@npm:^10.4.4 → npm:10.4.4
│     ├─ babel-loader@npm:^8.2.4 → npm:8.2.4
│     ├─ babel-plugin-dynamic-import-node@npm:2.3.0 → npm:2.3.0
│     ├─ boxen@npm:^6.2.1 → npm:6.2.1
│     ├─ chokidar@npm:^3.5.3 → npm:3.5.3
│     ├─ clean-css@npm:^5.2.4 → npm:5.3.0
│     ├─ cli-table3@npm:^0.6.1 → npm:0.6.1
│     ├─ combine-promises@npm:^1.1.0 → npm:1.1.0
│     ├─ commander@npm:^5.1.0 → npm:5.1.0
│     ├─ copy-webpack-plugin@npm:^10.2.4 → npm:10.2.4
│     ├─ core-js@npm:^3.21.1 → npm:3.21.1
│     ├─ css-loader@npm:^6.7.1 → npm:6.7.1
│     ├─ css-minimizer-webpack-plugin@npm:^3.4.1 → npm:3.4.1
│     ├─ cssnano@npm:^5.1.5 → npm:5.1.5
│     ├─ del@npm:^6.0.0 → npm:6.0.0
│     ├─ detect-port@npm:^1.3.0 → npm:1.3.0
│     ├─ escape-html@npm:^1.0.3 → npm:1.0.3
│     ├─ eta@npm:^1.12.3 → npm:1.12.3
│     ├─ file-loader@npm:^6.2.0 → npm:6.2.0
│     ├─ fs-extra@npm:^10.0.1 → npm:10.0.1
│     ├─ html-minifier-terser@npm:^6.1.0 → npm:6.1.0
│     ├─ html-tags@npm:^3.1.0 → npm:3.1.0
│     ├─ html-webpack-plugin@npm:^5.5.0 → npm:5.5.0
│     ├─ import-fresh@npm:^3.3.0 → npm:3.3.0
│     ├─ is-root@npm:^2.1.0 → npm:2.1.0
│     ├─ leven@npm:^3.1.0 → npm:3.1.0
│     ├─ lodash@npm:^4.17.21 → npm:4.17.21
│     ├─ mini-css-extract-plugin@npm:^2.6.0 → npm:2.6.0
│     ├─ nprogress@npm:^0.2.0 → npm:0.2.0
│     ├─ postcss-loader@npm:^6.2.1 → npm:6.2.1
│     ├─ postcss@npm:^8.4.12 → npm:8.4.12
│     ├─ prompts@npm:^2.4.2 → npm:2.4.2
│     ├─ react-dev-utils@npm:^12.0.0 → npm:12.0.0
│     ├─ react-helmet-async@npm:^1.2.3 → npm:1.2.3
│     ├─ react-loadable-ssr-addon-v5-slorber@npm:^1.0.1 → npm:1.0.1
│     ├─ react-loadable@npm:@docusaurus/react-loadable@5.5.2 → @docusaurus/react-loadable@npm:5.5.2
│     ├─ react-router-config@npm:^5.1.1 → npm:5.1.1
│     ├─ react-router-dom@npm:^5.2.0 → npm:5.3.0
│     ├─ react-router@npm:^5.2.0 → npm:5.2.1
│     ├─ remark-admonitions@npm:^1.2.1 → npm:1.2.1
│     ├─ rtl-detect@npm:^1.0.4 → npm:1.0.4
│     ├─ semver@npm:^7.3.5 → npm:7.3.5
│     ├─ serve-handler@npm:^6.1.3 → npm:6.1.3
│     ├─ shelljs@npm:^0.8.5 → npm:0.8.5
│     ├─ terser-webpack-plugin@npm:^5.3.1 → npm:5.3.1
│     ├─ tslib@npm:^2.3.1 → npm:2.3.1
│     ├─ update-notifier@npm:^5.1.0 → npm:5.1.0
│     ├─ url-loader@npm:^4.1.1 → npm:4.1.1
│     ├─ wait-on@npm:^6.0.1 → npm:6.0.1
│     ├─ webpack-bundle-analyzer@npm:^4.5.0 → npm:4.5.0
│     ├─ webpack-dev-server@npm:^4.7.4 → npm:4.7.4
│     ├─ webpack-merge@npm:^5.8.0 → npm:5.8.0
│     ├─ webpack@npm:^5.70.0 → npm:5.70.0
│     └─ webpackbar@npm:^5.0.2 → npm:5.0.2
│
├─ @docusaurus/preset-classic@npm:2.0.0-beta.18
│  ├─ Instances: 1
│  ├─ Version: 2.0.0-beta.18
│  │
│  └─ Dependencies
│     ├─ @docusaurus/core@npm:2.0.0-beta.18 → npm:2.0.0-beta.18
│     ├─ @docusaurus/plugin-content-blog@npm:2.0.0-beta.18 → npm:2.0.0-beta.18
│     ├─ @docusaurus/plugin-content-docs@npm:2.0.0-beta.18 → npm:2.0.0-beta.18
│     ├─ @docusaurus/plugin-content-pages@npm:2.0.0-beta.18 → npm:2.0.0-beta.18
│     ├─ @docusaurus/plugin-debug@npm:2.0.0-beta.18 → npm:2.0.0-beta.18
│     ├─ @docusaurus/plugin-google-analytics@npm:2.0.0-beta.18 → npm:2.0.0-beta.18
│     ├─ @docusaurus/plugin-google-gtag@npm:2.0.0-beta.18 → npm:2.0.0-beta.18
│     ├─ @docusaurus/plugin-sitemap@npm:2.0.0-beta.18 → npm:2.0.0-beta.18
│     ├─ @docusaurus/theme-classic@npm:2.0.0-beta.18 → npm:2.0.0-beta.18
│     ├─ @docusaurus/theme-common@npm:2.0.0-beta.18 → npm:2.0.0-beta.18
│     └─ @docusaurus/theme-search-algolia@npm:2.0.0-beta.18 → npm:2.0.0-beta.18
│
├─ @mdx-js/react@npm:1.6.22
│  ├─ Instances: 1
│  └─ Version: 1.6.22
│
├─ clsx@npm:1.1.1
│  └─ Version: 1.1.1
│
├─ jshint@npm:2.13.4
│  ├─ Version: 2.13.4
│  │
│  ├─ Exported Binaries
│  │  └─ jshint
│  │
│  └─ Dependencies
│     ├─ cli@npm:~1.0.0 → npm:1.0.1
│     ├─ console-browserify@npm:1.1.x → npm:1.1.0
│     ├─ exit@npm:0.1.x → npm:0.1.2
│     ├─ htmlparser2@npm:3.8.x → npm:3.8.3
│     ├─ lodash@npm:~4.17.21 → npm:4.17.21
│     ├─ minimatch@npm:~3.0.2 → npm:3.0.8
│     └─ strip-json-comments@npm:1.0.x → npm:1.0.4
│
├─ prism-react-renderer@npm:1.3.1
│  ├─ Instances: 1
│  └─ Version: 1.3.1
│
├─ react-dom@npm:17.0.2
│  ├─ Instances: 1
│  ├─ Version: 17.0.2
│  │
│  └─ Dependencies
│     ├─ loose-envify@npm:^1.1.0 → npm:1.4.0
│     ├─ object-assign@npm:^4.1.1 → npm:4.1.1
│     └─ scheduler@npm:^0.20.2 → npm:0.20.2
│
├─ react@npm:17.0.2
│  ├─ Version: 17.0.2
│  │
│  └─ Dependencies
│     ├─ loose-envify@npm:^1.1.0 → npm:1.4.0
│     └─ object-assign@npm:^4.1.1 → npm:4.1.1
│
└─ website@workspace:.
   ├─ Version: 0.0.0
   │
   └─ Dependencies
      ├─ clsx@npm:^1.1.1 → npm:1.1.1
      ├─ jshint@npm:^2.13.4 → npm:2.13.4
      ├─ react@npm:^17.0.2 → npm:17.0.2
      ├─ @docusaurus/core@npm:2.0.0-beta.18 → npm:2.0.0-beta.18 [8155a]
      ├─ @docusaurus/preset-classic@npm:2.0.0-beta.18 → npm:2.0.0-beta.18 [8155a]
      ├─ @mdx-js/react@npm:^1.6.22 → npm:1.6.22 [8155a]
      ├─ prism-react-renderer@npm:^1.3.1 → npm:1.3.1 [8155a]
      └─ react-dom@npm:^17.0.2 → npm:17.0.2 [8155a]
nik$ 

Using this manual method is just fine as a workaround until this issue gets fixed. There is a question though: will this manual deployment method allow me to use my domain rw-community.org and will successive manual deployment update the existing app at https://rw-community.org ?

hi there adriatic,

so that :point_up: error seems to indicate that there is a discrepance between your package.json file (which contains information on major versions of dependencies, but also lists out build commands and other information our robots need to know) and the yarn lock file (which tracks which versions, often minor versions - are actually installed). the lock file is important as it allows our service to create the exact same working configuration to what you might have locally. sometimes if you don’t have a lock file, minor versions or something can cause conflicts.

in order to fix this, i would take a closer look at your package.json and figure out what is going on with this website@workspace:.: package (which i am not sure is a legimitate package, and maybe doesn’t belong here?)

your best bet is always to get a local build of your project working, and then upload your project (without a node modules folder, but with the lock file) to our service, try clear cache and redeploy, and see if that helps. You should also check, if you have a gitignore file, that the lock file isn’t being ignored.

To your second question - yes, manual deployment will connect to rw-community.org as long as you are logged in to the netlify account that manages that site (which is connected to that domain). You can overwrite and update as normal until you figure out the problem.

let us know if this helps.