"No changes detected" after yarn build

aws-amplify / amplify-cli

The AWS Amplify CLI is a toolchain for simplifying serverless web and mobile development.

Apache License 2.0

2.83k stars 822 forks source link

"No changes detected" after yarn build #1644

Closed David-dp- closed 5 years ago

David-dp- commented 5 years ago

Note: If your question is regarding the AWS Amplify Console service, please log it in the official AWS Amplify Console forum

Which Category is your question related to?

push/publish

What AWS Services are you utilizing?

S3, CloudFront

Provide additional details e.g. code snippets

I'm able to "yarn start" and "yarn build" but "amplify push" says "No changes detected" even though I've edited my src/ and public/ and I see these changes after yarn start. (FWIW, I'm using Bash/Ubuntu/WSL after having no luck with PowerShell/Win10.)

I've Googled without good results for: amplify push with yarn

How do I push/publish when using yarn instead of npm? (npm gave me a different complaint about conflicting packages most times that I tried it.)

$ npm --version 3.10.10 $ yarn --version 1.16.0 $ node --version v10.16.0 $ amplify --version 1.7.1

$ amplify publish Current Environment: undefined

Category	Resource name	Operation	Provider plugin
Auth	modalityDevWebview	No Change	awscloudformation
Hosting	S3AndCloudFront	No Change	awscloudformation
Function	webviewDevCallflow	No Change	awscloudformation
Api	restfuldb	No Change	awscloudformation

No changes detected /mnt/c/Users/david/AppData/Local/Yarn/Data/global/node_modules/gluegun/build/index.js:13 throw up; ^

TypeError [ERR_INVALID_ARG_TYPE]: The "id" argument must be of type string. Received type undefined at validateString (internal/validators.js:125:11) at Module.require (internal/modules/cjs/loader.js:685:3) at require (internal/modules/cjs/helpers.js:25:18) at Command.run (/mnt/c/Users/david/AppData/Local/Yarn/Data/global/node_modules/@aws-amplify/cli/src/commands/publish.js:40:9) at process._tickCallback (internal/process/next_tick.js:68:7)

yuth commented 5 years ago

@David-dp- what version of Amplify CLI did you use when initializing the project?

From the error message, it looks like your project may have some missing config file. Could you try configuring your project once again by running amplify configure project.

If the above command does not work could you share the content inside your <proj-root>/amplify/.config/project-config.json

David-dp- commented 5 years ago

Thanks for responding so quickly, yuth.

I manually-edited project-config.json to change the npm start/build commands to what I thought the yarn equivalents should be; I couldn't find any guidance online. (I don't want to re-run amplify init, because I'm collaborating on a project where the main engineer is on vacation, and I don't know what to enter for, say, "Enter a name for the environment".) When I try to fix that, I get this error:

{project root}$ amplify configure project Error occured during configuration. { Error: ENOENT: no such file or directory, open '/mnt/e/{project root}/amplify/.config/local-env-info.json' at Object.openSync (fs.js:443:3) at Object.readFileSync (fs.js:343:35) at readJsonFile (/mnt/c/Users/david/AppData/Local/Yarn/Data/global/node_modules/@aws-amplify/cli/src/extensions/amplify-helpers/read-json-file.js:11:33) at Object.run (/mnt/c/Users/david/AppData/Local/Yarn/Data/global/node_modules/@aws-amplify/cli/src/lib/config-steps/c0-analyzeProject.js:15:34) at Command.run (/mnt/c/Users/david/AppData/Local/Yarn/Data/global/node_modules/@aws-amplify/cli/src/commands/configure.js:18:29) at Runtime. (/mnt/c/Users/david/AppData/Local/Yarn/Data/global/node_modules/gluegun/build/runtime/run.js:90:58) at step (/mnt/c/Users/david/AppData/Local/Yarn/Data/global/node_modules/gluegun/build/runtime/run.js:32:23) at Object.next (/mnt/c/Users/david/AppData/Local/Yarn/Data/global/node_modules/gluegun/build/runtime/run.js:13:53) at /mnt/c/Users/david/AppData/Local/Yarn/Data/global/node_modules/gluegun/build/runtime/run.js:7:71 at new Promise () errno: -2, syscall: 'open', code: 'ENOENT', path: '/mnt/e/{project root}/amplify/.config/local-env-info.json' } project-config.json.log

yuth commented 5 years ago

From the error it looks like your project is missing {project root}/amplify/.config/local-env-info.json which we added in Amplify CLI v1. Did you initialize your project with older version of CLI?

manually-edited project-config.json to change the npm start/build commands to what I thought the yarn equivalents should be; I couldn't find any guidance online.

You can run amplify configure project to update these start and build command.

David-dp- commented 5 years ago

The engineer who setup the project might have originally used a cli earlier than v1, but I have...

webview-dev$ yarn list @aws-amplify/cli yarn list v1.16.0 warning Filtering by arguments is deprecated. Please use the pattern option instead. └─ @aws-amplify/cli@1.7.1

If I run through amplify init again, is there a file or two that has the previous engineer's answers that I can use to give my answers? There seems to be no indicating of previous answers when I tried it today, so I did Ctrl+C when prompted for an environment name.

UPDATE: In WSL, I reinstalled python, pip, awscli, then re-did aws configure and amplify init. Because amplify init requires an env name, I chose "dev"; however, the engineer's s3 bucket is named "webviewdev-20181128134445-deployment" while my new one is "webview-dev-dev-20190612102928-deployment", so this suggests that the one he created Nov 2018 was using an amplify cli that didn't require an env name. (The project name is "webview-dev".)

amplify init ended with an error, but I think it can be ignored...

✔ Successfully created initial AWS cloud resources for deployments. init failed TypeError [ERR_INVALID_ARG_TYPE]: The "id" argument must be of type string. Received type undefined at validateString (internal/validators.js:125:11) at Module.require (internal/modules/cjs/loader.js:685:3) at require (internal/modules/cjs/helpers.js:25:18) at run (/mnt/c/Users/david/AppData/Local/Yarn/Data/global/node_modules/@aws-amplify/cli/src/lib/init-steps/s9-onSuccess.js:37:26) at process._tickCallback (internal/process/next_tick.js:68:7)

However, amplify push still doesn't notice my changes to src/ and public/

vada@Lemuria:/mnt/e/[deleted]/webview-dev$ amplify push

Current Environment: undefined

Category Resource name Operation Provider plugin

Auth modalityDevWebview No Change awscloudformation

Hosting S3AndCloudFront No Change awscloudformation

Function webviewDevCallflow No Change awscloudformation

Api restfuldb No Change awscloudformation

No changes detected

Also, retrying amplify configure project runs into the same problem with the missing local-env-info.json; I thought this should have been fixed by my rerunning amplify init, but perhaps the error I ran into there prevented it.

webview-dev$ amplify configure project Error occured during configuration. { Error: ENOENT: no such file or directory, open '/mnt/e/[deleted]/webview-dev/amplify/.config/local-env-info.json'

Then I manually created the missing file, and tried again:

$ amplify configure project ? Enter a name for the project webview-dev ? Choose your default editor: Atom Editor ? Choose the type of app that you're building javascript Please tell us about your project ? What javascript framework are you using react ? Source Directory Path: src ? Distribution Directory Path: build ? Build Command: yarn build ? Start Command: yarn start Using default provider awscloudformation Error occured during configuration. TypeError: currentProviders.includes is not a function at selectedProviders.forEach (/mnt/c/Users/david/AppData/Local/Yarn/Data/global/node_modules/@aws-amplify/cli/src/lib/config-steps/c2-configProviders.js:18:26) at Array.forEach () at run (/mnt/c/Users/david/AppData/Local/Yarn/Data/global/node_modules/@aws-amplify/cli/src/lib/config-steps/c2-configProviders.js:16:21) at process._tickCallback (internal/process/next_tick.js:68:7)

yuth commented 5 years ago

@David-dp- if the project is initialized with older version of Amplify we automatically migrate it. You could manually kick off the migration by running amplify migrate as documented. Please respond back in this issue if the migration fails

David-dp- commented 5 years ago

Thank you very much for pointing me to 'amplify migrate'. When I tried it, I had a couple issues:

1) The migrate page says "Note: The CLI would also prompt you to migrate your project when running any other amplify CLI commands on an older project after installing the new version of the cli," but I didn't see any prompts of that kind, so I think there's a bug in the cli. I shared my project as a zip with AWS Tech Support in case 6135856931, and they're monitoring this thread, so hopefully they will help identify why there have been no prompts to nudge me toward migration.

2) After amplify migrate, amplify push still says "No changes detected".

3) amplify publish throws an error (see below).

4) I had to use sudo to install the cli, contrary to the sample given at the top of https://aws-amplify.github.io/docs/cli/migrate I'm using Bash/Ubuntu/WSL, so I'd expect this to be a problem for any bash user.

Here's a trace of what I did today...

webview$ npm list @aws-amplify/cli modality-web-view@0.1.0 /mnt/e/[deleted]/webview └── (empty)

npm ERR! code 1

webview$ npm --version 3.10.10

webview$ npm install -g @aws-amplify/cli npm WARN deprecated circular-json@0.3.3: CircularJSON is in maintenance only, flatted is its successor. npm WARN deprecated left-pad@1.3.0: use String.prototype.padStart() npm WARN deprecated kleur@2.0.2: Please upgrade to kleur@3 or migrate to 'ansi-colors' if you prefer the old syntax. Visit https://github.com/lukeed/kleur/releases/tag/v3.0.0\ for migration path(s). npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue npm WARN checkPermissions Missing write access to /usr/local/lib/node_modules

webview$ sudo npm install -g @aws-amplify/cli

Renamed webview/amplify/.config/project-config.orig (as it's named in our repo) to project-config.json

webview$ amplify migrate webview$ amplify push

Current Environment: undefined

Category	Resource name	Operation	Provider plugin
Hosting	S3AndCloudFront	No Change	awscloudformation
Auth	modalityWebview	No Change	awscloudformation
Function	webviewCallflow	No Change	awscloudformation
Api	restfuldb	No Change	awscloudformation

No changes detected

webview$ amplify publish

Current Environment: undefined

Category	Resource name	Operation	Provider plugin
Hosting	S3AndCloudFront	No Change	awscloudformation
Auth	modalityWebview	No Change	awscloudformation
Function	webviewCallflow	No Change	awscloudformation
Api	restfuldb	No Change	awscloudformation

No changes detected /usr/local/lib/node_modules/@aws-amplify/cli/node_modules/gluegun/build/index.js:13 throw up; ^

TypeError [ERR_INVALID_ARG_TYPE]: The 'request' argument must be string. Received type undefined at /usr/local/lib/node_modules/@aws-amplify/cli/node_modules/esm/esm.js:1:224803 at Object. (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/esm/esm.js:1:251922) at Object.t (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/esm/esm.js:1:279775) at n (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/esm/esm.js:1:279589) at Command.run (/usr/local/lib/node_modules/@aws-amplify/cli/src/commands/publish.js:40:9) at process._tickCallback (internal/process/next_tick.js:68:7)

webview$ ls -l amplify/#current-cloud-backend/hosting/S3AndCloudFront total 8 -rwxrwxrwx 1 vada vada 8184 Nov 28 2018 template.json

yuth commented 5 years ago

@David-dp- thank you for sharing your project config files. I will investigate why you were not prompted to migrate.

From the logs I see that you have there a bunch of things missing. Could you check if the following files are present inside <proj-root>/amplify/.config

local-aws-info.json
local-env-info.json
project-config.json

If those are missing could you try to run amplify configure project and see if that solves the issue

David-dp- commented 5 years ago

Thank you. Here's the info you asked for...

webview$ ls -l amplify/.config/ total 0 -rwxrwxrwx 1 vada vada 90 Jun 3 12:18 aws-info.json -rwxrwxrwx 1 vada vada 482 May 29 14:45 project-config.json

webview$ amplify configure project

Error occured during configuration.
{ Error: ENOENT: no such file or directory, open '/mnt/e/[deleted]/webview/amplify/.config/local-env-info.json'
    at Object.openSync (fs.js:443:3)
    at Object.readFileSync (fs.js:343:35)
    at readJsonFile (/usr/local/lib/node_modules/@aws-amplify/cli/src/extensions/amplify-helpers/read-json-file.js:11:33)
    at Object.run (/usr/local/lib/node_modules/@aws-amplify/cli/src/lib/config-steps/c0-analyzeProject.js:15:34)
    at Command.run (/usr/local/lib/node_modules/@aws-amplify/cli/src/commands/configure.js:18:29)
    at Runtime.<anonymous> (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/gluegun/build/runtime/run.js:90:58)
    at step (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/gluegun/build/runtime/run.js:32:23)
    at Object.next (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/gluegun/build/runtime/run.js:13:53)
    at /usr/local/lib/node_modules/@aws-amplify/cli/node_modules/gluegun/build/runtime/run.js:7:71
    at new Promise (<anonymous>)
  errno: -2,
  syscall: 'open',
  code: 'ENOENT',
  path:
   '/mnt/e/[deleted]/webview/amplify/.config/local-env-info.json' }

yuth commented 5 years ago

In your shared zip file, amplify/.config folder is missing. Was it missing originally as well? If those files are missing, Amplify CLI can not detect if project needs migration.

To unblock you could you paste the following to your <project-root>/amplify/.confg/local-env-info.json and try running amplify configure project

{
    "projectName": "<project-name>",
    "version": "2.0",
    "frontend": "javascript",
    "javascript": {
        "framework": "none",
        "config": {
            "SourceDir": "src",
            "DistributionDir": "dist",
            "BuildCommand": "npm run-script build",
            "StartCommand": "npm run-script start"
        }
    },
    "providers": [
        "awscloudformation"
    ]
}

David-dp- commented 5 years ago

Sorry about that; Winzip left out the dot files. I've uploaded a corrected zip to the Case.

I tried your local-env-info.json, including setting the project-name, but it fails like earlier in this thread:

webview$ amplify configure project ? Enter a name for the project webview ? Choose your default editor: Atom Editor ? Choose the type of app that you're building javascript Please tell us about your project ? What javascript framework are you using react ? Source Directory Path: src ? Distribution Directory Path: build ? Build Command: npm run-script build ? Start Command: npm run-script start Using default provider awscloudformation Error occured during configuration. TypeError: currentProviders.includes is not a function at selectedProviders.forEach (/usr/local/lib/node_modules/@aws-amplify/cli/src/lib/config-steps/c2-configProviders.js:18:26) at Array.forEach () at run (/usr/local/lib/node_modules/@aws-amplify/cli/src/lib/config-steps/c2-configProviders.js:16:21) at process._tickCallback (internal/process/next_tick.js:68:7)

yuth commented 5 years ago

Could you update the following files with content pasted. Apologies that you have to do these manually. I pasted the wrong content in my earlier comment.

<project-root>/amplify/.confg/local-env-info.json

{
    "projectPath": "<project-root>",
    "defaultEditor": "code",
    "envName": "NONE"
}

<project-root>/amplify/.confg/project-config.json

{
    "projectName": "<project-name>",
    "version": "2.0",
    "frontend": "javascript",
    "javascript": {
        "framework": "none",
        "config": {
            "SourceDir": "src",
            "DistributionDir": "dist",
            "BuildCommand": "npm run-script build",
            "StartCommand": "npm run-script start"
        }
    },
    "providers": [
        "awscloudformation"
    ]
}

<project-root>/amplify/.confg/local-aws-info.json

{
    "dev": {
        "configLevel": "project",
        "useProfile": true,
        "profileName": "default"
    }
}

Now try to run amplify configure project and see if that helps

David-dp- commented 5 years ago

There are still problems. I provided details in the Case, and a new zip.

yuth commented 5 years ago

If you haven't made any changes to your backend resources, you would see "No change detected".

From the logs you pasted in Support case it looks like you don't have required dependecies installed in your project. Could you run yarn or npm install in your project directory before doing amplify publish so that all the needed node dependencies get installed

Also looking at your second zip file, it looks like your project was created with Amplify CLI > v1. So there was no need to migrate the amplify project and you were not prompted to do so.

David-dp- commented 5 years ago

1) If I make edits under src, I would expect that amplify push would notice. Or maybe only amplify publish will?

2) I re-ran npm install and ran into problems. Please see the trace attached. 2019-06-14_npmInstallInWebviewFails.log

3) My second zip file reflects changes I made using the manual edits you suggested recently; that's why it may appear that no migration is needed at this point. But anyone with a project as old as ours probably needs new support via amplify migrate to avoid such manual edits.

yuth commented 5 years ago

1. If I make edits under src, I would expect that amplify push would notice. Or maybe only amplify publish will?

No. src is for frontend resources, which are published. Amplify CLI considers only changes in your amplify/backend folder as changes that needs to be pushed. Publish looks at DistributionDir, which in your project happens to be <proj-root>/build. When you run amplify publish, amplify runs the build command that you set for your project and your build command should move any updated content that needs to be published

2\. I re-ran npm install and ran into problems. Please see the trace attached.
    [2019-06-14_npmInstallInWebviewFails.log](https://github.com/aws-amplify/amplify-cli/files/3288382/2019-06-14_npmInstallInWebviewFails.log)

Looks like you have some npm install issues which are not directly related to Amplify CLI. This might happen if you have an older version of NPM installed on your manchine. Try updating NPM and re-installing all the dependencies. Deleting node_modules before running npm install some times help.

3\. My second zip file reflects changes I made using the manual edits you suggested recently; that's why it may appear that no migration is needed at this point. But anyone with a project as old as ours probably needs new support via amplify migrate to avoid such manual edits.

It would be great if you could share the original project files so that we could figure out why you were not asked to migrate automatically. You can remove everything you have inside src directory before sharing as the content inside src won't have any use for the Amplify CLI debugging purposes

David-dp- commented 5 years ago

Hmm, I thought when I filed this issue that it would be clear that I'm only trying to update src and get that deployed. Everything I've read about amplify led me to think push or publish was the way to deploy. Would you point me to the docs about how to deploy a frontend from a src build?

Re: "Looks like you have some npm install issues which are not directly related to Amplify CLI. This might happen if you have an older version of NPM installed on your manchine." I've repeatedly run into problems trying to install npm on Ubuntu/WSL. The normal Linux method seems not to work on WSL, and the best advice I've found is...

Following https://www.youtube.com/watch?v=hiWWXCZbY6A for installing node on WSL: sudo apt-get remove node nodejs npm sudo apt-get install -y nodejs sudo npm cache clean sudo npm install n -g sudo n stable sudo ln -sf /usr/local/bin/node /usr/bin/node node -v sudo apt-get purge -y nodejs

David-dp- commented 5 years ago

So...if it's possible to use yarn instead of npm, and deploy that frontend using our current aws method, that would remove a major obstacle.

yuth commented 5 years ago

Amplify CLI works with both Yarn and NPM. The issue you encountered is not specific to the packaging system, but might an issue with our migration scripts. I am trying to reproduce migration failure, but haven't been able to do that.

Have you managed publish the changes successfully ?

David-dp- commented 5 years ago

Almost all my calls to 'amplify publish' (after successful yarn start and yarn build) result in ENOENT of some kind.

I have tried installing @aws-amplify/cli via npm as global, npm as local to the project, and via 'yarn global add'. I'm not sure of the significance of the '@' and whether it should have been included in the latter variants.

I do recall once not getting an error, but there was no obvious upload of the frontend. I believe this trace was shared here or in the case.

kaustavghosh06 commented 5 years ago

@David-dp- Can you try running your app locally and see if you encounter this error? (Using npm start or whatever run command you use to start the app locally.)

David-dp- commented 5 years ago

@kaustavghosh06 I've been able to run yarn start successfully many times. Right now it has an error due to a src change I've made, but otherwise it's worked fine. FWIW, this is in sister project webview-dev, created at the same time as the prod project shared to the case, webview. They have nearly identical backends. In order to stay close to your site's instructions, I've used npm instead of yarn in the debugging we've done recently, so all the modules under webiew were installed via npm.

In both projects, 'amplify publish' either encounters an error, or does no upload of my frontend and merely ends with "No changes detected".

kaustavghosh06 commented 5 years ago

@David-dp- Also, locally can you check if you can run npm run-script build & npm run-script start successfully after fixing errors in your src?

David-dp- commented 5 years ago

I think you're asking me to do that in webview, because I would expect it to fail in webview-dev where node_modules was populated by yarn install.

yuth commented 5 years ago

From your applications point of view both npm install and yarn install should not change anything. Both of them install the dependencies of your project and they npm run-script build and npm run-script start should work fine.

In both projects, 'amplify publish' either encounters an error, or does no upload of my frontend and merely ends with "No changes detected".

Do you get the same error as you attached earlier? If not could you include the error

David-dp- commented 5 years ago

I just asked the npm project for help: https://npm.community/t/what-is-the-recommended-way-of-installing-for-windows-subsystem-for-linux-wsl/8219

vada@Lemuria:~$ cd /mnt/e/[deleted]/webview vada@Lemuria:/mnt/e/[deleted]/webview$ npm run-script build

modality-web-view@0.1.0 build /mnt/e/[deleted]/webview react-scripts build

sh: 1: react-scripts: not found

npm ERR! Linux 4.4.0-17134-Microsoft npm ERR! argv "/usr/local/bin/node" "/usr/bin/npm" "run-script" "build" npm ERR! node v10.16.0 npm ERR! npm v3.10.10 npm ERR! file sh npm ERR! code ELIFECYCLE npm ERR! errno ENOENT npm ERR! syscall spawn npm ERR! modality-web-view@0.1.0 build: react-scripts build npm ERR! spawn ENOENT npm ERR! npm ERR! Failed at the modality-web-view@0.1.0 build script 'react-scripts build'. npm ERR! Make sure you have the latest version of node.js and npm installed. npm ERR! If you do, this is most likely a problem with the modality-web-view package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! react-scripts build npm ERR! You can get information on how to open an issue for this project with: npm ERR! npm bugs modality-web-view npm ERR! Or if that isn't available, you can get their info via: npm ERR! npm owner ls modality-web-view npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request: npm ERR! /mnt/e/[deleted]/webview/npm-debug.log

vada@Lemuria:/mnt/e/[deleted]/webview$ npm install npm WARN deprecated core-js@1.2.7: core-js@<2.6.8 is no longer maintained. Please, upgrade to core-js@3 or at least to actual version of core-js@2. npm WARN deprecated left-pad@1.3.0: use String.prototype.padStart() npm WARN deprecated flatten@1.0.2: I wrote this module a very long time ago; you should use something else. npm ERR! tar.unpack untar error /home/vada/.npm/argparse/1.0.10/package.tgz npm ERR! tar.unpack untar error /home/vada/.npm/minimist/1.2.0/package.tgz npm ERR! tar.unpack untar error /home/vada/.npm/eslint-plugin-flowtype/2.50.1/package.tgz npm ERR! tar.unpack untar error /home/vada/.npm/regenerate-unicode-properties/8.1.0/package.tgz npm ERR! tar.unpack untar error /home/vada/.npm/eslint-plugin-jsx-a11y/6.2.1/package.tgz npm ERR! tar.unpack untar error /home/vada/.npm/jsdom/11.12.0/package.tgz npm ERR! tar.unpack untar error /home/vada/.npm/aws-sdk/2.329.0/package.tgz npm ERR! tar.unpack untar error /home/vada/.npm/date-fns/2.0.0-alpha.34/package.tgz modality-web-view@0.1.0 /mnt/e/[deleted]/webview ├── @webassemblyjs/ast@1.8.5 extraneous ├─┬ glamor@2.20.40 │ ├─┬ fbjs@0.8.17 │ │ ├── core-js@1.2.7 │ │ ├─┬ isomorphic-fetch@2.2.1 │ │ │ ├─┬ node-fetch@1.7.3 │ │ │ │ ├─┬ encoding@0.1.12 │ │ │ │ │ └─┬ iconv-lite@0.4.24 │ │ │ │ │ └── safer-buffer@2.1.2 │ │ │ │ └── is-stream@1.1.0 │ │ │ └── whatwg-fetch@3.0.0 │ │ ├─┬ promise@7.3.1 │ │ │ └── asap@2.0.6 │ │ ├── setimmediate@1.0.5 │ │ └── ua-parser-js@0.7.20 │ ├─┬ inline-style-prefixer@3.0.8 │ │ ├── bowser@1.9.4 │ │ └─┬ css-in-js-utils@2.0.1 │ │ ├── hyphenate-style-name@1.0.3 │ │ └── isobject@3.0.1 │ ├── object-assign@4.1.1 │ ├─┬ prop-types@15.7.2 │ │ └── react-is@16.8.6 │ └── through@2.3.8 ├── moment@2.24.0 ├─┬ query-string@6.7.0 │ ├── decode-uri-component@0.2.0 │ ├── split-on-first@1.1.0 │ └── strict-uri-encode@2.0.0 ├─┬ react@16.8.6 │ ├─┬ loose-envify@1.4.0 │ │ └── js-tokens@4.0.0 │ └── scheduler@0.13.6 ├─┬ react-bootstrap@1.0.0-beta.9 │ ├─┬ @babel/runtime@7.4.5 │ │ └── regenerator-runtime@0.13.2 │ ├─┬ @react-bootstrap/react-popper@1.2.1 │ │ ├─┬ babel-runtime@6.26.0 │ │ │ ├── core-js@2.6.9 │ │ │ └── regenerator-runtime@0.11.1 │ │ ├─┬ create-react-context@0.2.3 │ │ │ └── gud@1.0.0 │ │ ├── typed-styles@0.0.5 │ │ └── warning@3.0.0 │ ├── @restart/context@2.1.4 │ ├── @restart/hooks@0.3.1 │ ├── classnames@2.2.6 │ ├── dom-helpers@3.4.0 │ ├── invariant@2.2.4 │ ├── keycode@2.2.0 │ ├── popper.js@1.15.0 │ ├─┬ prop-types-extra@1.1.0 │ │ └── warning@3.0.0 │ ├─┬ react-overlays@1.2.0 │ │ ├── react-context-toolbox@2.0.2 │ │ └─┬ react-popper@1.3.3 │ │ ├── create-react-context@0.2.2 │ │ └── typed-styles@0.0.7 │ ├── react-transition-group@4.1.1 │ ├── uncontrollable@6.1.0 │ └── warning@4.0.3 ├── react-dom@16.8.6 ├── react-files@2.4.8 ├─┬ react-loading-overlay@1.0.1 │ ├─┬ emotion@10.0.9 │ │ ├─┬ babel-plugin-emotion@10.0.13 │ │ │ ├─┬ @babel/helper-module-imports@7.0.0 │ │ │ │ └─┬ @babel/types@7.4.4 │ │ │ │ ├── esutils@2.0.2 │ │ │ │ ├── lodash@4.17.11 │ │ │ │ └── to-fast-properties@2.0.0 │ │ │ ├── @emotion/hash@0.7.1 │ │ │ ├── @emotion/memoize@0.7.1 │ │ │ ├─┬ @emotion/serialize@0.11.7 │ │ │ │ ├── @emotion/unitless@0.7.3 │ │ │ │ └── csstype@2.6.5 │ │ │ ├─┬ babel-plugin-macros@2.6.1 │ │ │ │ ├─┬ cosmiconfig@5.2.1 │ │ │ │ │ ├─┬ import-fresh@2.0.0 │ │ │ │ │ │ ├─┬ caller-path@2.0.0 │ │ │ │ │ │ │ └─┬ caller-callsite@2.0.0 │ │ │ │ │ │ │ └── callsites@2.0.0 │ │ │ │ │ │ └── resolve-from@3.0.0 │ │ │ │ │ ├── is-directory@0.3.1 │ │ │ │ │ └─┬ parse-json@4.0.0 │ │ │ │ │ ├─┬ error-ex@1.3.2 │ │ │ │ │ │ └── is-arrayish@0.2.1 │ │ │ │ │ └── json-parse-better-errors@1.0.2 │ │ │ │ └─┬ resolve@1.11.0 │ │ │ │ └── path-parse@1.0.6 │ │ │ ├── babel-plugin-syntax-jsx@6.18.0 │ │ │ ├─┬ convert-source-map@1.6.0 │ │ │ │ └── safe-buffer@5.1.2 │ │ │ ├── escape-string-regexp@1.0.5 │ │ │ ├── find-root@1.1.0 │ │ │ └── source-map@0.5.7 │ │ └─┬ create-emotion@10.0.9 │ │ ├─┬ @emotion/cache@10.0.9 │ │ │ ├── @emotion/stylis@0.8.3 │ │ │ └── @emotion/weak-memoize@0.2.2 │ │ ├── @emotion/sheet@0.9.2 │ │ └── @emotion/utils@0.11.1 │ └─┬ react-transition-group@2.9.0 │ └── react-lifecycles-compat@3.0.4 ├─┬ react-router-dom@4.3.1 │ ├─┬ history@4.9.0 │ │ ├── resolve-pathname@2.2.0 │ │ ├── tiny-invariant@1.0.4 │ │ ├── tiny-warning@1.0.2 │ │ └── value-equal@0.4.0 │ └─┬ react-router@4.3.1 │ ├── hoist-non-react-statics@2.5.5 │ └─┬ path-to-regexp@1.7.0 │ └── isarray@0.0.1 ├── ts-react-json-table@0.1.2 └── typescript@3.5.2

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.0.6 (node_modules/react-scripts/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.0.6: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_modules/jest-haste-map/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_modules/chokidar/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: minimist@1.2.0 (node_modules/minimist): npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, utime '/mnt/e/[deleted]/webview/node_modules/.staging/minimist-c68606f9/test/long.js' npm WARN optional SKIPPING OPTIONAL DEPENDENCY: eslint-plugin-flowtype@2.50.1 (node_modules/eslint-plugin-flowtype): npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, utime '/mnt/e/[deleted]/webview/node_modules/.staging/eslint-plugin-flowtype-338c39d1/dist/rules/booleanStyle.js' npm WARN optional SKIPPING OPTIONAL DEPENDENCY: regenerate-unicode-properties@8.1.0 (node_modules/regenerate-unicode-properties): npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, utime '/mnt/e/[deleted]/webview/node_modules/.staging/regenerate-unicode-properties-f69d26ef/Binary_Property/Pattern_White_Space.js' npm WARN optional SKIPPING OPTIONAL DEPENDENCY: eslint-plugin-jsx-a11y@6.2.1 (node_modules/eslint-plugin-jsx-a11y): npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, utime '/mnt/e/[deleted]/webview/node_modules/.staging/eslint-plugin-jsx-a11y-d40de854/tests/src/rules/no-noninteractive-element-interactions-test.js' npm WARN optional SKIPPING OPTIONAL DEPENDENCY: jsdom@11.12.0 (node_modules/jsdom): npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, utime '/mnt/e/[deleted]/webview/node_modules/.staging/jsdom-d1807ecf/lib/jsdom/living/generated/FocusEventInit.js' npm ERR! Linux 4.4.0-17134-Microsoft npm ERR! argv "/usr/local/bin/node" "/usr/bin/npm" "install" npm ERR! node v10.16.0 npm ERR! npm v3.10.10 npm ERR! path /mnt/e/[deleted]/webview/node_modules/.staging/argparse-4e108390/README.md npm ERR! code ENOENT npm ERR! errno -2 npm ERR! syscall utime

npm ERR! enoent ENOENT: no such file or directory, utime '/mnt/e/[deleted]/webview/node_modules/.staging/argparse-4e108390/README.md' npm ERR! enoent ENOENT: no such file or directory, utime '/mnt/e/[deleted]/webview/node_modules/.staging/argparse-4e108390/README.md' npm ERR! enoent This is most likely not a problem with npm itself npm ERR! enoent and is related to npm not being able to find a file. npm ERR! enoent

npm ERR! Please include the following file with any support request: npm ERR! /mnt/e/[deleted]/webview/npm-debug.log

David-dp- commented 5 years ago

If you have a machine for testing on WSL or PowerShell, I would be very interested to know how you installed node, npm, aws-amplify/cli, and then npm install for my package.json.

jkeys-ecg-nmsu commented 5 years ago

@David-dp- are you launching your WSL Ubuntu shell as administrator, and are you running these commands as superuser?

I develop on WSL/Ubuntu at my job and most commands work on it.

Can you try rm -rf node_modules && sudo npm install?

David-dp- commented 5 years ago

Thanks, Jeremy. I wouldn't have guessed that one needs Windows Admin permission to use sudo in WSL, but I just tried it. I'm still getting untar errors:

$ rm -rf node_modules && sudo npm install
[sudo] password for vada:
npm WARN deprecated core-js@1.2.7: core-js@<2.6.8 is no longer maintained. Please, upgrade to core-js@3 or at least to actual version of core-js@2.
npm WARN deprecated left-pad@1.3.0: use String.prototype.padStart()
npm WARN deprecated flatten@1.0.2: I wrote this module a very long time ago; you should use something else.
npm ERR! tar.unpack untar error /home/vada/.npm/follow-redirects/1.5.10/package.tgz
npm ERR! tar.unpack untar error /home/vada/.npm/browserify-aes/1.2.0/package.tgz
npm ERR! tar.unpack untar error /home/vada/.npm/keycode/2.2.0/package.tgz
npm ERR! tar.unpack untar error /home/vada/.npm/core-js/2.6.9/package.tgz

For the record, I started this way today:

WindowsKey + s
Entered: ubuntu
Right-clicked on the match to select Run as admin

jkeys-ecg-nmsu commented 5 years ago

Not sure about this one, this Github issue suggests running npm cache clean may resolve your error.

David-dp- commented 5 years ago

I noticed the .npm folder, and guessed it was a cache, so I interrupted the install via Ctrl+c and retried. But I still get many untar errors...

$ sudo npm cache clean [sudo] password for vada: vada@Lemuria:/mnt/e/[deleted]/webview$ rm -rf node_modules && sudo npm install npm WARN deprecated core-js@1.2.7: core-js@<2.6.8 is no longer maintained. Please, upgrade to core-js@3 or at least to actual version of core-js@2. npm WARN deprecated left-pad@1.3.0: use String.prototype.padStart() npm WARN deprecated flatten@1.0.2: I wrote this module a very long time ago; you should use something else. npm ERR! tar.unpack untar error /home/vada/.npm/ignore/4.0.6/package.tgz npm ERR! tar.unpack untar error /home/vada/.npm/css-tree/1.0.0-alpha.28/package.tgz npm ERR! tar.unpack untar error /home/vada/.npm/events/1.1.1/package.tgz npm ERR! tar.unpack untar error /home/vada/.npm/cssstyle/1.2.2/package.tgz npm ERR! tar.unpack untar error /home/vada/.npm/eslint-plugin-react/7.12.4/package.tgz npm ERR! tar.unpack untar error /home/vada/.npm/core-js/3.0.1/package.tgz npm ERR! tar.unpack untar error /home/vada/.npm/core-js/1.2.7/package.tgz npm ERR! tar.unpack untar error /home/vada/.npm/rxjs/6.5.2/package.tgz npm ERR! tar.unpack untar error /home/vada/.npm/caniuse-lite/1.0.30000974/package.tgz npm ERR! tar.unpack untar error /home/vada/.npm/aws-sdk/2.474.0/package.tgz modality-web-view@0.1.0 /mnt/e/[deleted]/webview ├── @webassemblyjs/ast@1.8.5 extraneous ├─┬ glamor@2.20.40 │ ├─┬ inline-style-prefixer@3.0.8 │ │ ├── bowser@1.9.4 │ │ └─┬ css-in-js-utils@2.0.1 │ │ ├── hyphenate-style-name@1.0.3 │ │ └── isobject@3.0.1 │ ├── object-assign@4.1.1 │ ├─┬ prop-types@15.7.2 │ │ └── react-is@16.8.6 │ └── through@2.3.8 ├── moment@2.24.0 ├─┬ query-string@6.7.0 │ ├── decode-uri-component@0.2.0 │ ├── split-on-first@1.1.0 │ └── strict-uri-encode@2.0.0 ├─┬ react@16.8.6 │ ├─┬ loose-envify@1.4.0 │ │ └── js-tokens@4.0.0 │ └── scheduler@0.13.6 ├─┬ react-datepicker@2.7.0 │ ├── classnames@2.2.6 │ ├── date-fns@2.0.0-alpha.34 │ └── react-onclickoutside@6.8.0 ├── react-dom@16.8.6 ├── react-files@2.4.8 ├─┬ react-loading-overlay@1.0.1 │ ├─┬ emotion@10.0.9 │ │ ├─┬ babel-plugin-emotion@10.0.13 │ │ │ ├─┬ @babel/helper-module-imports@7.0.0 │ │ │ │ └─┬ @babel/types@7.4.4 │ │ │ │ ├── esutils@2.0.2 │ │ │ │ ├── lodash@4.17.11 │ │ │ │ └── to-fast-properties@2.0.0 │ │ │ ├── @emotion/hash@0.7.1 │ │ │ ├── @emotion/memoize@0.7.1 │ │ │ ├─┬ @emotion/serialize@0.11.7 │ │ │ │ ├── @emotion/unitless@0.7.3 │ │ │ │ └── csstype@2.6.5 │ │ │ ├─┬ babel-plugin-macros@2.6.1 │ │ │ │ ├─┬ cosmiconfig@5.2.1 │ │ │ │ │ ├─┬ import-fresh@2.0.0 │ │ │ │ │ │ ├─┬ caller-path@2.0.0 │ │ │ │ │ │ │ └─┬ caller-callsite@2.0.0 │ │ │ │ │ │ │ └── callsites@2.0.0 │ │ │ │ │ │ └── resolve-from@3.0.0 │ │ │ │ │ ├── is-directory@0.3.1 │ │ │ │ │ ├─┬ js-yaml@3.13.1 │ │ │ │ │ │ ├─┬ argparse@1.0.10 │ │ │ │ │ │ │ └── sprintf-js@1.0.3 │ │ │ │ │ │ └── esprima@4.0.1 │ │ │ │ │ └─┬ parse-json@4.0.0 │ │ │ │ │ ├─┬ error-ex@1.3.2 │ │ │ │ │ │ └── is-arrayish@0.2.1 │ │ │ │ │ └── json-parse-better-errors@1.0.2 │ │ │ │ └─┬ resolve@1.11.0 │ │ │ │ └── path-parse@1.0.6 │ │ │ ├── babel-plugin-syntax-jsx@6.18.0 │ │ │ ├─┬ convert-source-map@1.6.0 │ │ │ │ └── safe-buffer@5.1.2 │ │ │ ├── escape-string-regexp@1.0.5 │ │ │ ├── find-root@1.1.0 │ │ │ └── source-map@0.5.7 │ │ └─┬ create-emotion@10.0.9 │ │ ├─┬ @emotion/cache@10.0.9 │ │ │ ├── @emotion/stylis@0.8.3 │ │ │ └── @emotion/weak-memoize@0.2.2 │ │ ├── @emotion/sheet@0.9.2 │ │ └── @emotion/utils@0.11.1 │ └─┬ react-transition-group@2.9.0 │ ├── dom-helpers@3.4.0 │ └── react-lifecycles-compat@3.0.4 ├─┬ react-router-dom@4.3.1 │ ├─┬ history@4.9.0 │ │ ├─┬ @babel/runtime@7.4.5 │ │ │ └── regenerator-runtime@0.13.2 │ │ ├── resolve-pathname@2.2.0 │ │ ├── tiny-invariant@1.0.4 │ │ ├── tiny-warning@1.0.2 │ │ └── value-equal@0.4.0 │ ├── invariant@2.2.4 │ ├─┬ react-router@4.3.1 │ │ ├── hoist-non-react-statics@2.5.5 │ │ └─┬ path-to-regexp@1.7.0 │ │ └── isarray@0.0.1 │ └── warning@4.0.3 ├── ts-react-json-table@0.1.2 └── typescript@3.5.2

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.0.6 (node_modules/react-scripts/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.0.6: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_modules/jest-haste-map/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_modules/chokidar/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: css-tree@1.0.0-alpha.28 (node_modules/css-tree): npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, utime '/mnt/e/[deleted]/webview/node_modules/.staging/css-tree-a1b7a6d2/data/patch.json' npm WARN optional SKIPPING OPTIONAL DEPENDENCY: cssstyle@1.2.2 (node_modules/cssstyle): npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, utime '/mnt/e/[deleted]/webview/node_modules/.staging/cssstyle-24df450a/lib/properties/backgroundPosition.js' npm WARN optional SKIPPING OPTIONAL DEPENDENCY: eslint-plugin-react@7.12.4 (node_modules/eslint-plugin-react): npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, utime '/mnt/e/[deleted]/webview/node_modules/.staging/eslint-plugin-react-5a1b5244/lib/rules/no-unsafe.js' npm WARN optional SKIPPING OPTIONAL DEPENDENCY: core-js@3.0.1 (node_modules/react-app-polyfill/node_modules/core-js): npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, utime '/mnt/e/[deleted]/webview/node_modules/.staging/core-js-8338bf89/es/object/get-prototype-of.js' npm WARN optional SKIPPING OPTIONAL DEPENDENCY: rxjs@6.5.2 (node_modules/rxjs): npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, utime '/mnt/e/[deleted]/webview/node_modules/.staging/rxjs-6b1c55b8/_esm2015/internal/operators/takeWhile.js.map' npm WARN optional SKIPPING OPTIONAL DEPENDENCY: caniuse-lite@1.0.30000974 (node_modules/caniuse-lite): npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, utime '/mnt/e/[deleted]/webview/node_modules/.staging/caniuse-lite-81405ece/data/regions/alt-as.js' npm WARN optional SKIPPING OPTIONAL DEPENDENCY: aws-sdk@2.474.0 (node_modules/aws-sdk): npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, utime '/mnt/e/[deleted]/webview/node_modules/.staging/aws-sdk-e294d9d9/lib/polly/presigner.js' npm ERR! Linux 4.4.0-17134-Microsoft npm ERR! argv "/usr/local/bin/node" "/usr/bin/npm" "install" npm ERR! node v10.16.0 npm ERR! npm v3.10.10 npm ERR! path /mnt/e/[deleted]/webview/node_modules/.staging/ignore-65503d6f/CHANGELOG.md npm ERR! code ENOENT npm ERR! errno -2 npm ERR! syscall utime

npm ERR! enoent ENOENT: no such file or directory, utime '/mnt/e/[deleted]/webview/node_modules/.staging/ignore-65503d6f/CHANGELOG.md' npm ERR! enoent ENOENT: no such file or directory, utime '/mnt/e/[deleted]/webview/node_modules/.staging/ignore-65503d6f/CHANGELOG.md' npm ERR! enoent This is most likely not a problem with npm itself npm ERR! enoent and is related to npm not being able to find a file. npm ERR! enoent

npm ERR! Please include the following file with any support request: npm ERR! /mnt/e/[deleted]/webview/npm-debug.log

jkeys-ecg-nmsu commented 5 years ago

Last thing I can think of is package-lock.json might be affecting your install process. Can you delete that file and try again?

David-dp- commented 5 years ago

I made some progress, as noted in https://npm.community/t/what-is-the-recommended-way-of-installing-for-windows-subsystem-for-linux-wsl/8219/3?u=david-dp It seems that the sudo permission is expiring midway. I've started installing each item in my package.json manually, e.g. sudo npm install glamor@2.20.40 It would probably be easier and work just as well if I had 'sudo su' before 'npm install'. I'll try your suggestion of deleting package-lock.json if needed, but I've done that many times already in past attempts.

David-dp- commented 5 years ago

Even after starting with 'sudo su', I get many ENOENT problems. I think this is due to poor handling by npm of network timeouts or Windows filepath length limits. It would be great to hear how I could get my yarn build deployed to AWS in the meantime.

I still can't get all the dependencies of my project satisfied. I'm in New Zealand, and it seems network timeouts just can't be overcome from here recently. I looked for a nearby npm registry, but it seems there are none.

jkeys-ecg-nmsu commented 5 years ago

@David-dp- quick and dirty:

Build your source (npm run build / yarn build);
Look up the S3 hosting bucket from your Amplify-gen'd CloudFormation template
Upload your build folder to this bucket
Look up the CloudFront CDN (if prod) from the CF template
Invalidate the * path to tell CDN to go to the bucket to get the latest version of the site

Step 1 seems to be where you're stuck at, if you can't figure out the build process I'd just let a CI tool do it for you.

David-dp- commented 5 years ago

@jkeys-ecg-nmsu Thank you very much. For step 2, I looked in ((project))\amplify#current-cloud-backend\amplify-meta.json under hosting/output/HostingBucketName. In a folder for debugging, I placed a backup: aws s3 sync s3://((bucket name)) . Then I deleted everything in the bucket (which seems to accumulate old files with every publish) and uploaded the contents of my 'build' folder.

Steps 4 and 5 weren't necessary in my case.

Also, I believe your side is working on:

amplify publish doesn't nudge me toward migration
amplify migrate finishes silently for me and doesn't change anything

I'd be happy to test, if you have a candidate for these. I'm using @aws-amplify/cli v1.7.1 now.

jkeys-ecg-nmsu commented 5 years ago

I should probably clarify that I don't work for AWS and am not contributing to the Amplify source directly. Just a good Samaritan helping others avoid headache over solved problems. @yuth may be able to comment more on your last two concerns.

On Wed, Jun 19, 2019 at 12:07 PM David-dp- notifications@github.com wrote:

@jkeys-ecg-nmsu https://github.com/jkeys-ecg-nmsu Thank you very much. For step 2, I looked in ((project))\amplify#current-cloud-backend\amplify-meta.json under hosting/output/HostingBucketName. In a folder for debugging, I placed a backup: aws s3 sync s3://((bucket name)) . Then I deleted everything in the bucket (which seems to accumulate old files with every publish) and uploaded the contents of my 'build' folder.

Steps 4 and 5 weren't necessary in my case.

Also, I believe your side is working on:

amplify publish doesn't nudge me toward migration

amplify migrate finishes silently for me and doesn't change anything

I'd be happy to test, if you have a candidate for these.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/aws-amplify/amplify-cli/issues/1644?email_source=notifications&email_token=AFPGTXW75VN52K4YNWJRUFDP3J7VLA5CNFSM4HW4N3F2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYC3GEI#issuecomment-503690001, or mute the thread https://github.com/notifications/unsubscribe-auth/AFPGTXTR5CLNJROXEMSAVRDP3J7VLANCNFSM4HW4N3FQ .

-- Software Developer Electronic Caregiver

UnleashedMind commented 5 years ago

@David-dp-

What's the current status of this issue?

I tested our latest version 1.7.5 on Windows 10, and there's no issue with that setup. So, you can probably just run the commands on cmd.exe or power shell on a Windows 10 directly.

Make sure that you have those three files inside your amplify/.config folder

/amplify/.config/local-aws-info.json /amplify/.config/local-env-info.json /amplify/.config/project-config.json

David-dp- commented 5 years ago

@UnleashedMind Because https://github.com/aws-amplify/amplify-cli says "If you're using Windows, the CLI currently supports Windows Subsystem for Linux," but it doesn't work for me on WSL, I'm offering to test fixes re:

amplify publish doesn't nudge me toward migration
amplify migrate finishes silently for me and doesn't change anything

When I offered this yesterday, I was on v1.7.1. I just tested again and somehow I upgraded myself to 1.7.4, but 'amplify migrate' still finishes silently on my circa-Nov2018 project config, and amplify publish results in an error still.

I just did: yarn global add @aws-amplify/cli@1.7.5.

Migrate still finishes silently, and git doesn't see that it made any file changes, but it does take about a minute to finish now instead of returning immediately.
Publish ends in an error...

/mnt/e/[deleted]/webview$ amplify publish

Current Environment: undefined

Category	Resource name	Operation	Provider plugin
Hosting	S3AndCloudFront	No Change	awscloudformation
Auth	modalityWebview	No Change	awscloudformation
Function	webviewCallflow	No Change	awscloudformation
Api	restfuldb	No Change	awscloudformation

No changes detected

modality-web-view@0.1.0 build /mnt/e/[deleted]/webview react-scripts build

Creating an optimized production build... BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all BrowserslistError: Unknown browser query android all Compiled successfully.

File sizes after gzip:

370.22 KB build/static/js/2.fb8a32e9.chunk.js 12.21 KB build/static/js/main.01223c9a.chunk.js 2.6 KB build/static/css/2.b9944180.chunk.css 905 B build/static/css/main.b75123cd.chunk.css 762 B build/static/js/runtime~main.a8a9905a.js

The project was built assuming it is hosted at the server root. You can control this with the homepage field in your package.json. For example, add this to build it for GitHub Pages:

"homepage" : "http://myname.github.io/myapp",

The build folder is ready to be deployed. You may serve it with a static server:

yarn global add serve serve -s build

Find out more about deployment here:

https://bit.ly/CRA-deploy

frontend build command exited with code 0 /usr/local/lib/node_modules/@aws-amplify/cli/node_modules/gluegun/build/index.js:13 throw up; ^

TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received type undefined at validateString (internal/validators.js:125:11) at Proxy.join (path.js:1147:7) at publishToHostingBucket (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/amplify-frontend-javascript/lib/publisher.js:19:36) at process._tickCallback (internal/process/next_tick.js:68:7)

David-dp- commented 5 years ago

@jkeys-ecg-nmsu The quick-and-dirty upload process started failing today. Even after clearing app data in the browser, emptying cache, and doing a hard reload, the browser keeps indicating:

Resource interpreted as Stylesheet but transferred with MIME type text/html: "https://((my domain))/static/css/main.950db643.chunk.css".

I can find many google hits about this, including https://stackoverflow.com/a/52573915/6856046 but none of them seem relevant to the build method I've been using so far (i.e. yarn build)

attilah commented 5 years ago

@David-dp- I took a look at your issue and I think this is not related to your project or Amplify CLI itself, but to your environment on your machine, please help me confirm it.

I setup a Windows 10 WSL fresh and installed awscli, nvm, node 10 (via nvm), git and then I was able to create projects and I had no errors like you had.

I used Windows 10 1903 and Ubuntu from the Windows Store.

The steps I used to setup the fresh WSL instance are these:

Update and Upgrade

sudo apt update && sudo apt upgrade

Install tools

# Install nvm dependencies
echo "# Installing nvm dependencies"
sudo apt-get -y install build-essential libssl-dev

curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.34.0/install.sh | bash

# Set up nvm environment without restarting the shell
export NVM_DIR="${HOME}/.nvm"
[ -s "${NVM_DIR}/nvm.sh" ] && . "${NVM_DIR}/nvm.sh"
[ -s "${NVM_DIR}/bash_completion" ] && . "${NVM_DIR}/bash_completion"

# Install node
nvm install 10
nvm use 10

# Ensure that CA certificates are installed
sudo apt-get -y install apt-transport-https ca-certificates

sudo apt-get install yarn
export PATH="$PATH:`yarn global bin`"

AWS Tools

sudo apt install awscli  
aws configure

Amplify CLI

npm i -g @aws-amplify/cli

These were the steps I performed to get a working environment

Based on your logs and comments you already sent I suspect that you've yarn and node installed under Windows and it flows into your WSL environment.

Please confirm that you've these installed or not.
Please send me the result of echo $PATH command.
Please send me the result of these:
- which node
- which yarn
- yarn global bin

Since I was in your logs/comments that you've yarn global is under your %LOCALAPPDATA% folder I think the Windows installed yarn is running under your WSL and perhaps it is true for node as well and that can cause problems, and we need the linux binaries to run under WSL to ensure maximum compatibility.

If the above suspicion is correct please clean up your $PATH to make sure that you are running the Linux version of the tools.

David-dp- commented 5 years ago

@attilah I really appreciate your suggestions.

I believe the ENOENT errors at the bottom of this comment may reveal something helpful, not sure, but I'll stop for now until I hear from you.

About my current setup: I've used a Windows install of node for years, but when I started having problems with npm install, I used Revo Uninstaller Pro to remove it. I have Win10 os build 17* which I believe is the public stable current version. And I have Ubuntu for WSL from the Windows Store, installed once I had problems with the Windows-installer's node and saw on the aws-amplify/cli page that WSL is supported (but it wasn't clear that Win-native node is). FWIW, my WSL user, vada, is different from the Windows user that I use for all my Windows-native work, david.

Just now, because I saw Yarn in my PATH on a Windows-native folderpath, I used Revo Uninstaller Pro to remove it. After reboot, Winkey+s shows no match for node nor yarn. And neither appears in my PATH now.

In Ubuntu/WSL launched as Admin:

vada@Lemuria:~$ echo $PATH
/home/vada/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/mnt/c/Program Files (x86)/Common Files/Oracle/Java/javapath_target_736000046:/mnt/c/ProgramData/Oracle/Java/javapath_target_1481236406:/mnt/c/Program Files (x86)/Intel/iCLS Client:/mnt/c/Program Files/Intel/iCLS Client:/mnt/c/Windows/System32:/mnt/c/Windows:/mnt/c/Windows/System32/wbem:/mnt/c/Windows/System32/WindowsPowerShell/v1.0:/mnt/c/Program Files/Intel/Intel(R) Management Engine Components/DAL:/mnt/c/Program Files/Intel/Intel(R) Management Engine Components/IPT:/mnt/c/Program Files (x86)/Intel/Intel(R) Management Engine Components/DAL:/mnt/c/Program Files (x86)/Intel/Intel(R) Management Engine Components/IPT:/mnt/c/Program Files/Intel/WiFi/bin:/mnt/c/Program Files/Common Files/Intel/WirelessCommon:/mnt/c/ProgramData/Lenovo/ReadyApps:/mnt/c/Tools-DavidP/MinimalGnuWindows/bin:/mnt/c/Program Files (x86)/GnuWin32/bin:/mnt/c/Program Files/Microsoft SQL Server/110/Tools/Binn:/mnt/c/Program Files (x86)/GtkSharp/2.12/bin:/mnt/c/Program Files (x86)/Boxcryptor/bin:/mnt/c/Program Files/AMI/DuOS:/mnt/c/Program Files/Git/cmd:/mnt/c/Windows/System32/OpenSSH:/mnt/c/Program Files (x86)/Plantronics/Spokes3G:/mnt/c/Program Files/KDiff3:/mnt/c/Program Files (x86)/sox-14-4-2:/mnt/c/Users/david/AppData/Local/Microsoft/WindowsApps:/mnt/c/Users/david/AppData/Local/atom/bin

vada@Lemuria:~$ which node
/usr/local/bin/node

vada@Lemuria:~$ which yarn
/usr/bin/yarn

vada@Lemuria:~$ yarn global bin
/home/vada/.yarn/bin

sudo apt update && sudo apt upgrade
[omitted]
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

sudo apt-get -y install build-essential libssl-dev
[Did install some things]

curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.34.0/install.sh | bash
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 13226  100 13226    0     0  26652      0 --:--:-- --:--:-- --:--:-- 26719
=> Downloading nvm from git to '/home/vada/.nvm'
=> Initialized empty Git repository in /home/vada/.nvm/.git/
remote: Enumerating objects: 278, done.
remote: Counting objects: 100% (278/278), done.
remote: Compressing objects: 100% (249/249), done.
remote: Total 278 (delta 33), reused 88 (delta 16), pack-reused 0
Receiving objects: 100% (278/278), 142.36 KiB | 0 bytes/s, done.
Resolving deltas: 100% (33/33), done.
From https://github.com/creationix/nvm
 * [new tag]         v0.34.0    -> v0.34.0
=> Compressing and cleaning up git repository

=> nvm source string already in /home/vada/.bashrc
=> bash_completion source string already in /home/vada/.bashrc
npm ERR! error in /usr/local/lib/node_modules/npm: ENOENT: no such file or directory, open '/usr/local/lib/node_modules/npm/package.json'
npm ERR! extraneous: cacache /usr/local/lib/node_modules/npm/node_modules/cacache
npm ERR! error in /usr/local/lib/node_modules/npm/node_modules/cacache: ENOENT: no such file or directory, open '/usr/local/lib/node_modules/npm/node_modules/cacache/package.json'
npm ERR! extraneous: cliui /usr/local/lib/node_modules/npm/node_modules/cliui
npm ERR! error in /usr/local/lib/node_modules/npm/node_modules/cliui: ENOENT: no such file or directory, open '/usr/local/lib/node_modules/npm/node_modules/cliui/package.json'
npm ERR! extraneous: copy-concurrently /usr/local/lib/node_modules/npm/node_modules/copy-concurrently
npm ERR! error in /usr/local/lib/node_modules/npm/node_modules/copy-concurrently: ENOENT: no such file or directory, open '/usr/local/lib/node_modules/npm/node_modules/copy-concurrently/package.json'
npm ERR! extraneous: execa /usr/local/lib/node_modules/npm/node_modules/execa
npm ERR! error in /usr/local/lib/node_modules/npm/node_modules/execa: ENOENT: no such file or directory, open '/usr/local/lib/node_modules/npm/node_modules/execa/package.json'
npm ERR! extraneous: fs-write-stream-atomic /usr/local/lib/node_modules/npm/node_modules/fs-write-stream-atomic
npm ERR! error in /usr/local/lib/node_modules/npm/node_modules/fs-write-stream-atomic: ENOENT: no such file or directory, open '/usr/local/lib/node_modules/npm/node_modules/fs-write-stream-atomic/package.json'
npm ERR! extraneous: gauge /usr/local/lib/node_modules/npm/node_modules/gauge
npm ERR! error in /usr/local/lib/node_modules/npm/node_modules/gauge: ENOENT: no such file or directory, open '/usr/local/lib/node_modules/npm/node_modules/gauge/package.json'
npm ERR! extraneous: gentle-fs /usr/local/lib/node_modules/npm/node_modules/gentle-fs
npm ERR! error in /usr/local/lib/node_modules/npm/node_modules/gentle-fs: ENOENT: no such file or directory, open '/usr/local/lib/node_modules/npm/node_modules/gentle-fs/package.json'
npm ERR! extraneous: got /usr/local/lib/node_modules/npm/node_modules/got
npm ERR! error in /usr/local/lib/node_modules/npm/node_modules/got: ENOENT: no such file or directory, open '/usr/local/lib/node_modules/npm/node_modules/got/package.json'
npm ERR! extraneous: libnpmaccess /usr/local/lib/node_modules/npm/node_modules/libnpmaccess
npm ERR! error in /usr/local/lib/node_modules/npm/node_modules/libnpmaccess: ENOENT: no such file or directory, open '/usr/local/lib/node_modules/npm/node_modules/libnpmaccess/package.json'
npm ERR! extraneous: libnpmconfig /usr/local/lib/node_modules/npm/node_modules/libnpmconfig
npm ERR! error in /usr/local/lib/node_modules/npm/node_modules/libnpmconfig: ENOENT: no such file or directory, open '/usr/local/lib/node_modules/npm/node_modules/libnpmconfig/package.json'
npm ERR! extraneous: libnpmorg /usr/local/lib/node_modules/npm/node_modules/libnpmorg
npm ERR! error in /usr/local/lib/node_modules/npm/node_modules/libnpmorg: ENOENT: no such file or directory, open '/usr/local/lib/node_modules/npm/node_modules/libnpmorg/package.json'
npm ERR! extraneous: libnpmteam /usr/local/lib/node_modules/npm/node_modules/libnpmteam
npm ERR! error in /usr/local/lib/node_modules/npm/node_modules/libnpmteam: ENOENT: no such file or directory, open '/usr/local/lib/node_modules/npm/node_modules/libnpmteam/package.json'
npm ERR! extraneous: minipass /usr/local/lib/node_modules/npm/node_modules/minipass
npm ERR! error in /usr/local/lib/node_modules/npm/node_modules/minipass: ENOENT: no such file or directory, open '/usr/local/lib/node_modules/npm/node_modules/minipass/package.json'
npm ERR! extraneous: move-concurrently /usr/local/lib/node_modules/npm/node_modules/move-concurrently
npm ERR! error in /usr/local/lib/node_modules/npm/node_modules/move-concurrently: ENOENT: no such file or directory, open '/usr/local/lib/node_modules/npm/node_modules/move-concurrently/package.json'
npm ERR! extraneous: node-gyp /usr/local/lib/node_modules/npm/node_modules/node-gyp
npm ERR! error in /usr/local/lib/node_modules/npm/node_modules/node-gyp: ENOENT: no such file or directory, open '/usr/local/lib/node_modules/npm/node_modules/node-gyp/package.json'
npm ERR! extraneous: agentkeepalive@3.4.1 /usr/local/lib/node_modules/npm/node_modules/agentkeepalive
npm ERR! extraneous: ansi-regex@2.1.1 /usr/local/lib/node_modules/npm/node_modules/ansi-regex
npm ERR! extraneous: ansi-styles@3.2.1 /usr/local/lib/node_modules/npm/node_modules/ansi-styles
npm ERR! extraneous: aproba@2.0.0 /usr/local/lib/node_modules/npm/node_modules/aproba
npm ERR! extraneous: asap@2.0.6 /usr/local/lib/node_modules/npm/node_modules/asap
npm ERR! extraneous: aws-sign2@0.7.0 /usr/local/lib/node_modules/npm/node_modules/aws-sign2
npm ERR! extraneous: aws4@1.8.0 /usr/local/lib/node_modules/npm/node_modules/aws4
npm ERR! extraneous: block-stream@0.0.9 /usr/local/lib/node_modules/npm/node_modules/block-stream
npm ERR! extraneous: bluebird@3.5.3 /usr/local/lib/node_modules/npm/node_modules/bluebird
npm ERR! extraneous: buffer-from@1.0.0 /usr/local/lib/node_modules/npm/node_modules/buffer-from
npm ERR! extraneous: builtins@1.0.3 /usr/local/lib/node_modules/npm/node_modules/builtins
npm ERR! extraneous: byline@5.0.0 /usr/local/lib/node_modules/npm/node_modules/byline
npm ERR! extraneous: camelcase@4.1.0 /usr/local/lib/node_modules/npm/node_modules/camelcase
npm ERR! extraneous: caseless@0.12.0 /usr/local/lib/node_modules/npm/node_modules/caseless
npm ERR! extraneous: cidr-regex@2.0.10 /usr/local/lib/node_modules/npm/node_modules/cidr-regex
npm ERR! extraneous: cli-boxes@1.0.0 /usr/local/lib/node_modules/npm/node_modules/cli-boxes
npm ERR! extraneous: cmd-shim@2.0.2 /usr/local/lib/node_modules/npm/node_modules/cmd-shim
npm ERR! extraneous: code-point-at@1.1.0 /usr/local/lib/node_modules/npm/node_modules/code-point-at
npm ERR! extraneous: colors@1.3.3 /usr/local/lib/node_modules/npm/node_modules/colors
npm ERR! extraneous: console-control-strings@1.1.0 /usr/local/lib/node_modules/npm/node_modules/console-control-strings
npm ERR! extraneous: core-util-is@1.0.2 /usr/local/lib/node_modules/npm/node_modules/core-util-is
npm ERR! extraneous: create-error-class@3.0.2 /usr/local/lib/node_modules/npm/node_modules/create-error-class
npm ERR! extraneous: crypto-random-string@1.0.0 /usr/local/lib/node_modules/npm/node_modules/crypto-random-string
npm ERR! extraneous: cyclist@0.2.2 /usr/local/lib/node_modules/npm/node_modules/cyclist
npm ERR! extraneous: dashdash@1.14.1 /usr/local/lib/node_modules/npm/node_modules/dashdash
npm ERR! extraneous: debuglog@1.0.1 /usr/local/lib/node_modules/npm/node_modules/debuglog
npm ERR! extraneous: decamelize@1.2.0 /usr/local/lib/node_modules/npm/node_modules/decamelize
npm ERR! extraneous: decode-uri-component@0.2.0 /usr/local/lib/node_modules/npm/node_modules/decode-uri-component
npm ERR! extraneous: deep-extend@0.5.1 /usr/local/lib/node_modules/npm/node_modules/deep-extend
npm ERR! extraneous: defaults@1.0.3 /usr/local/lib/node_modules/npm/node_modules/defaults
npm ERR! extraneous: delegates@1.0.0 /usr/local/lib/node_modules/npm/node_modules/delegates
npm ERR! extraneous: dot-prop@4.2.0 /usr/local/lib/node_modules/npm/node_modules/dot-prop
npm ERR! extraneous: dotenv@5.0.1 /usr/local/lib/node_modules/npm/node_modules/dotenv
npm ERR! extraneous: duplexer3@0.1.4 /usr/local/lib/node_modules/npm/node_modules/duplexer3
npm ERR! extraneous: err-code@1.1.2 /usr/local/lib/node_modules/npm/node_modules/err-code
npm ERR! extraneous: escape-string-regexp@1.0.5 /usr/local/lib/node_modules/npm/node_modules/escape-string-regexp
npm ERR! extraneous: extend@3.0.2 /usr/local/lib/node_modules/npm/node_modules/extend
npm ERR! extraneous: extsprintf@1.3.0 /usr/local/lib/node_modules/npm/node_modules/extsprintf
npm ERR! extraneous: figgy-pudding@3.5.1 /usr/local/lib/node_modules/npm/node_modules/figgy-pudding
npm ERR! extraneous: find-npm-prefix@1.0.2 /usr/local/lib/node_modules/npm/node_modules/find-npm-prefix
npm ERR! extraneous: forever-agent@0.6.1 /usr/local/lib/node_modules/npm/node_modules/forever-agent
npm ERR! extraneous: form-data@2.3.2 /usr/local/lib/node_modules/npm/node_modules/form-data
npm ERR! extraneous: fs.realpath@1.0.0 /usr/local/lib/node_modules/npm/node_modules/fs.realpath
npm ERR! extraneous: genfun@5.0.0 /usr/local/lib/node_modules/npm/node_modules/genfun
npm ERR! extraneous: get-caller-file@1.0.2 /usr/local/lib/node_modules/npm/node_modules/get-caller-file
npm ERR! extraneous: getpass@0.1.7 /usr/local/lib/node_modules/npm/node_modules/getpass
npm ERR! extraneous: global-dirs@0.1.1 /usr/local/lib/node_modules/npm/node_modules/global-dirs
npm ERR! extraneous: har-validator@5.1.0 /usr/local/lib/node_modules/npm/node_modules/har-validator
npm ERR! extraneous: has-flag@3.0.0 /usr/local/lib/node_modules/npm/node_modules/has-flag
npm ERR! extraneous: has-unicode@2.0.1 /usr/local/lib/node_modules/npm/node_modules/has-unicode
npm ERR! extraneous: hosted-git-info@2.7.1 /usr/local/lib/node_modules/npm/node_modules/hosted-git-info
npm ERR! extraneous: http-cache-semantics@3.8.1 /usr/local/lib/node_modules/npm/node_modules/http-cache-semantics
npm ERR! extraneous: http-proxy-agent@2.1.0 /usr/local/lib/node_modules/npm/node_modules/http-proxy-agent
npm ERR! extraneous: https-proxy-agent@2.2.1 /usr/local/lib/node_modules/npm/node_modules/https-proxy-agent
npm ERR! extraneous: import-lazy@2.1.0 /usr/local/lib/node_modules/npm/node_modules/import-lazy
npm ERR! extraneous: imurmurhash@0.1.4 /usr/local/lib/node_modules/npm/node_modules/imurmurhash
npm ERR! extraneous: ip@1.1.5 /usr/local/lib/node_modules/npm/node_modules/ip
npm ERR! extraneous: is-ci@1.1.0 /usr/local/lib/node_modules/npm/node_modules/is-ci
npm ERR! extraneous: is-fullwidth-code-point@1.0.0 /usr/local/lib/node_modules/npm/node_modules/is-fullwidth-code-point
npm ERR! extraneous: is-npm@1.0.0 /usr/local/lib/node_modules/npm/node_modules/is-npm
npm ERR! extraneous: is-redirect@1.0.0 /usr/local/lib/node_modules/npm/node_modules/is-redirect
npm ERR! extraneous: is-retry-allowed@1.1.0 /usr/local/lib/node_modules/npm/node_modules/is-retry-allowed
npm ERR! extraneous: is-stream@1.1.0 /usr/local/lib/node_modules/npm/node_modules/is-stream
npm ERR! extraneous: is-typedarray@1.0.0 /usr/local/lib/node_modules/npm/node_modules/is-typedarray
npm ERR! extraneous: isarray@1.0.0 /usr/local/lib/node_modules/npm/node_modules/isarray
npm ERR! extraneous: isexe@2.0.0 /usr/local/lib/node_modules/npm/node_modules/isexe
npm ERR! extraneous: isstream@0.1.2 /usr/local/lib/node_modules/npm/node_modules/isstream
npm ERR! extraneous: jsbn@0.1.1 /usr/local/lib/node_modules/npm/node_modules/jsbn
npm ERR! extraneous: json-parse-better-errors@1.0.2 /usr/local/lib/node_modules/npm/node_modules/json-parse-better-errors
npm ERR! extraneous: json-schema@0.2.3 /usr/local/lib/node_modules/npm/node_modules/json-schema
npm ERR! extraneous: json-stringify-safe@5.0.1 /usr/local/lib/node_modules/npm/node_modules/json-stringify-safe
npm ERR! extraneous: jsonparse@1.3.1 /usr/local/lib/node_modules/npm/node_modules/jsonparse
npm ERR! extraneous: lcid@1.0.0 /usr/local/lib/node_modules/npm/node_modules/lcid
npm ERR! extraneous: lodash._createset@4.0.3 /usr/local/lib/node_modules/npm/node_modules/lodash._createset
npm ERR! extraneous: lodash._getnative@3.9.1 /usr/local/lib/node_modules/npm/node_modules/lodash._getnative
npm ERR! extraneous: lodash._root@3.0.1 /usr/local/lib/node_modules/npm/node_modules/lodash._root
npm ERR! extraneous: lodash.clonedeep@4.5.0 /usr/local/lib/node_modules/npm/node_modules/lodash.clonedeep
npm ERR! extraneous: lowercase-keys@1.0.1 /usr/local/lib/node_modules/npm/node_modules/lowercase-keys
npm ERR! extraneous: mem@1.1.0 /usr/local/lib/node_modules/npm/node_modules/mem
npm ERR! extraneous: mute-stream@0.0.7 /usr/local/lib/node_modules/npm/node_modules/mute-stream
npm ERR! extraneous: npm-logical-tree@1.2.1 /usr/local/lib/node_modules/npm/node_modules/npm-logical-tree
npm ERR! extraneous: npm-packlist@1.4.1 /usr/local/lib/node_modules/npm/node_modules/npm-packlist
npm ERR! extraneous: oauth-sign@0.9.0 /usr/local/lib/node_modules/npm/node_modules/oauth-sign
npm ERR! extraneous: object-assign@4.1.1 /usr/local/lib/node_modules/npm/node_modules/object-assign
npm ERR! extraneous: osenv@0.1.5 /usr/local/lib/node_modules/npm/node_modules/osenv
npm ERR! extraneous: p-finally@1.0.0 /usr/local/lib/node_modules/npm/node_modules/p-finally
=> You currently have modules installed globally with `npm`. These will no
=> longer be linked to the active version of Node when you install a new node
=> with `nvm`; and they may (depending on how you construct your `$PATH`)
=> override the binaries of modules installed with `nvm`:

/usr/local/lib
├── @aws-amplify/cli@1.7.4
├── n@4.1.0
└──  error: ENOENT: no such file or directory, open '/usr/local/lib/node_modules/npm/package.json
=> If you wish to uninstall them at a later point (or re-install them under your
=> `nvm` Nodes), you can remove them from the system Node as follows:

     $ nvm use system
     $ npm uninstall -g a_module

=> Close and reopen your terminal to start using nvm or run the following to use it now:

export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"  # This loads nvm
[ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion"  # This loads nvm bash_completion

attilah commented 5 years ago

@David-dp- I forgot to emphasize that I did not run WSL as admin, I see no need for that, just as usual.

Since your WSL environment had some struggle, would you agree to reset it and try the steps I outline above to see if that would make a difference or not?

Resetting WSL:

Go to Settings app on Windows
Apps -> Apps & Features
In the list search for Ubuntu and after selecting it click Advanced options
Click the Reset button.

Personally I prefer not to mix windows paths into my $PATH because back in the day when I used Windows it caused some - hard to troubleshoot - problems.

I think that the ENOENT errors are happening because the file/folder permissions are mixed up.

David-dp- commented 5 years ago

@attilah When I searched for Ubuntu in Apps&Features, there was no match. The only Linux-related app I found was GnuWin32:CoreUtils v5.3.0 (which I believe my Git GUI uses). This is very surprising, because my WSL terminal indicated it was Ubuntu.

When I installed Ubuntu for WSL about a month ago, I did so via the Microsoft Store app, and several times, using its Get button had no effect. IIRC, I reopened the Store and might have rebooted to finish Ubuntu install.

Just now, I went back into the Store, found Ubuntu 18.04 LTS https://www.microsoft.com/store/productId/9N9TNGVNDL3Q and installed it. After launching its terminal, I created a new user. But echo $PATH still shows Windows-native folderpaths. I agree that not relying on Windows-native apps in WSL would be best, but I'm not sure if I can alter this PATH without disturbing my Windows apps.

To try to start on a clean slate, I rebooted, and reset the new Ubuntu.

I also noticed that I still had a taskbar pin for the old Ubuntu, and its shortcut says it's at: C:\Windows\System32\bash.exe ~ That exe still exists and has a mod date of Dec 4, 2018. I'll leave it for now and use the new Ubuntu terminal exclusively. This bash.exe seems to be the same discussed in this WSL article: https://www.howtogeek.com/261188/how-to-uninstall-or-reinstall-windows-10s-ubuntu-bash-shell/ Unfortunately, the only match for Winkey+s ubuntu is this bash.exe. That seemed due to the Reset, so I opened Store and launched Ubuntu there. I recreated my user, and now Winkey+s ubuntu has a match for this app also.

bird@Lemuria:~$ echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/mnt/c/Program Files/WindowsApps/CanonicalGroupLimited.Ubuntu18.04onWindows_1804.2019.522.0_x64__79rhkp1fndgsc:/mnt/c/Program Files (x86)/Common Files/Oracle/Java/javapath_target_736000046:/mnt/c/ProgramData/Oracle/Java/javapath_target_1481236406:/mnt/c/Program Files (x86)/Intel/iCLS Client:/mnt/c/Program Files/Intel/iCLS Client:/mnt/c/Windows/System32:/mnt/c/Windows:/mnt/c/Windows/System32/wbem:/mnt/c/Windows/System32/WindowsPowerShell/v1.0:/mnt/c/Program Files/Intel/Intel(R) Management Engine Components/DAL:/mnt/c/Program Files/Intel/Intel(R) Management Engine Components/IPT:/mnt/c/Program Files (x86)/Intel/Intel(R) Management Engine Components/DAL:/mnt/c/Program Files (x86)/Intel/Intel(R) Management Engine Components/IPT:/mnt/c/Program Files/Intel/WiFi/bin:/mnt/c/Program Files/Common Files/Intel/WirelessCommon:/mnt/c/ProgramData/Lenovo/ReadyApps:/mnt/c/Tools-DavidP/MinimalGnuWindows/bin:/mnt/c/Program Files (x86)/GnuWin32/bin:/mnt/c/Program Files/Microsoft SQL Server/110/Tools/Binn:/mnt/c/Program Files (x86)/GtkSharp/2.12/bin:/mnt/c/Program Files (x86)/Boxcryptor/bin:/mnt/c/Program Files/AMI/DuOS:/mnt/c/Program Files/Git/cmd:/mnt/c/Windows/System32/OpenSSH:/mnt/c/Program Files (x86)/Plantronics/Spokes3G:/mnt/c/Program Files/KDiff3:/mnt/c/Program Files (x86)/sox-14-4-2:/mnt/c/Users/david/AppData/Local/Microsoft/WindowsApps:/mnt/c/Users/david/AppData/Local/atom/bin:/snap/bin

I returned to your install directions from 3 days ago: https://github.com/aws-amplify/amplify-cli/issues/1644#issuecomment-506882092 But for any lines starting with sudo, I instead entered sudo su, did the command, and then exited -- to avoid the sudo timeout, which I believe is 5 mins.

After yarn installation:

bird@Lemuria:~$ export PATH="$PATH:`yarn global bin`"
00h00m00s 0/0: : ERROR: [Errno 2] No such file or directory: 'global'
bird@Lemuria:~$ which yarn
/usr/bin/yarn

I had no problems this time with npm install, npm start, nor npm run-script build. However, amplify still misbehaves in the same ways:

bird@Lemuria:/mnt/e/[omitted]/webview-dev$ npm run-script build

> webview-dev@0.1.0 build /mnt/e/[omitted]/webview-dev
> react-scripts build

Creating an optimized production build...
Compiled successfully.

File sizes after gzip:

  413.78 KB (+32.54 KB)  build/static/js/2.829220b3.chunk.js
  12.89 KB (+21 B)       build/static/js/main.95a5ccc7.chunk.js
  2.59 KB                build/static/css/2.c7bb94bc.chunk.css
  1.03 KB                build/static/css/main.170fa2db.chunk.css
  762 B                  build/static/js/runtime~main.a8a9905a.js

The project was built assuming it is hosted at the server root.
You can control this with the homepage field in your package.json.
For example, add this to build it for GitHub Pages:

  "homepage" : "http://myname.github.io/myapp",

The build folder is ready to be deployed.
You may serve it with a static server:

  npm install -g serve
  serve -s build

Find out more about deployment here:

  https://bit.ly/CRA-deploy

bird@Lemuria:/mnt/e/[omitted]/webview-dev$ amplify publish

Current Environment: undefined

| Category | Resource name      | Operation | Provider plugin   |
| -------- | ------------------ | --------- | ----------------- |
| Auth     | modalityDevWebview | No Change | awscloudformation |
| Hosting  | S3AndCloudFront    | No Change | awscloudformation |
| Function | webviewDevCallflow | No Change | awscloudformation |
| Api      | restfuldb          | No Change | awscloudformation |

No changes detected
/home/bird/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/gluegun/build/index.js:13
    throw up;
    ^

TypeError [ERR_INVALID_ARG_TYPE]: The 'request' argument must be string. Received type undefined
    at /home/bird/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/esm/esm.js:1:224803
    at Object.<anonymous> (/home/bird/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/esm/esm.js:1:251922)
    at Object.t (/home/bird/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/esm/esm.js:1:279775)
    at n (/home/bird/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/node_modules/esm/esm.js:1:279589)
    at Command.run (/home/bird/.nvm/versions/node/v10.16.0/lib/node_modules/@aws-amplify/cli/src/commands/publish.js:40:9)
    at process._tickCallback (internal/process/next_tick.js:68:7)
bird@Lemuria:/mnt/e/[omitted]/webview-dev$ amplify migrate
bird@Lemuria:/mnt/e/[omitted]/webview-dev$ amplify --version
1.7.8
bird@Lemuria:/mnt/e/[omitted]/webview-dev$ npm --version
6.9.0
bird@Lemuria:/mnt/e/[omitted]/webview-dev$ node --version
v10.16.0

kaustavghosh06 commented 5 years ago

@David-dp- Were you able to debug your issue? CLosing this since it looks like a platform specific concern.

David-dp- commented 5 years ago

Platform specific? Amplify migrate is silent for a pre-1.0 project.

On Fri, 9 Aug 2019, 5:48 am Kaustav Ghosh, notifications@github.com wrote:

@David-dp- https://github.com/David-dp- Were you able to debug your issue? CLosing this since it looks like a platform specific concern.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/aws-amplify/amplify-cli/issues/1644?email_source=notifications&email_token=AA5RKQ6KDC3JAISTT4EQ7OLQDRL6NA5CNFSM4HW4N3F2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD34MRXQ#issuecomment-519620830, or mute the thread https://github.com/notifications/unsubscribe-auth/AA5RKQ7OQYTDYOAGNXFAX5DQDRL6NANCNFSM4HW4N3FQ .

shlomizadok commented 5 years ago

Happens to me as well in circle ci using circleci/node:10.15.0-jessie which is Ubuntu based image

#!/bin/bash -eo pipefail
./node_modules/.bin/amplify publish
Scanning for plugins...
Plugin scan successful

Current Environment: beta

| Category  | Resource name   | Operation | Provider plugin   |
| --------- | --------------- | --------- | ----------------- |
| Auth      | cognito...      | No Change | awscloudformation |
| Analytics | ....beta        | No Change | awscloudformation |
| Hosting   | S3AndCloudFront | No Change | awscloudformation |
| Api       | our...api       | No Change |                   |

No changes detected
The 'request' argument must be string. Received type undefined
TypeError [ERR_INVALID_ARG_TYPE]: The 'request' argument must be string. Received type undefined
    at /home/circleci/repo/node_modules/esm/esm.js:1:224803
    at Object.<anonymous> (/home/circleci/repo/node_modules/esm/esm.js:1:251922)
    at Object.t (/home/circleci/repo/node_modules/esm/esm.js:1:279775)
    at n (/home/circleci/repo/node_modules/esm/esm.js:1:279589)
    at /home/circleci/repo/node_modules/@aws-amplify/cli/lib/commands/publish.js:80:45
    at step (/home/circleci/repo/node_modules/@aws-amplify/cli/lib/commands/publish.js:33:23)
    at Object.next (/home/circleci/repo/node_modules/@aws-amplify/cli/lib/commands/publish.js:14:53)
    at fulfilled (/home/circleci/repo/node_modules/@aws-amplify/cli/lib/commands/publish.js:5:58)
    at process._tickCallback (internal/process/next_tick.js:68:7)

Would love a direction to solve this

attilah commented 5 years ago

@David-dp- @shlomizadok could you please delete your package.lock.json or its yarn counterpart and try it that way? Also observe the changes perhaps you can spot something meaningful.

shlomizadok commented 5 years ago

Thanks for the help (and apologies in advance for the long paste below) I trigger a manual installation of amplify-cli on my circle-ci build. Here's the output of the installation:

#!/bin/bash -eo pipefail
yarn add @aws-amplify/cli
yarn add v1.12.3
[1/4] Resolving packages...
warning @aws-amplify/cli > @types/ora@3.2.0: This is a stub types definition. ora provides its own type definitions, so you do not need this installed.
warning @aws-amplify/cli > amplify-util-mock > amplify-appsync-simulator > @conduitvc/mosca > ascoltatori > node-uuid@1.4.8: Use uuid module instead
warning @aws-amplify/cli > amplify-util-mock > amplify-appsync-simulator > @conduitvc/mosca > ascoltatori > kafka-node > node-uuid@1.4.8: Use uuid module instead
[2/4] Fetching packages...
info fsevents@1.2.9: The platform "linux" is incompatible with this module.
info "fsevents@1.2.9" is an optional dependency and failed compatibility check. Excluding it from installation.
info fsevents@2.0.6: The platform "linux" is incompatible with this module.
info "fsevents@2.0.6" is an optional dependency and failed compatibility check. Excluding it from installation.
info fsevents@2.0.7: The platform "linux" is incompatible with this module.
info "fsevents@2.0.7" is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
warning "aws-appsync > apollo-link-http@1.3.1" has incorrect peer dependency "graphql@^0.11.0".
warning "react-apollo > apollo-utilities@1.3.2" has unmet peer dependency "graphql@^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0".
warning " > bootstrap@4.3.1" has unmet peer dependency "jquery@1.9.1 - 3".
warning " > bootstrap@4.3.1" has unmet peer dependency "popper.js@^1.14.7".
warning " > react-apollo@2.5.8" has unmet peer dependency "apollo-client@^2.6.3".
warning " > react-apollo@2.5.8" has unmet peer dependency "graphql@^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0".
warning "react-scripts > @typescript-eslint/eslint-plugin@1.6.0" has unmet peer dependency "typescript@*".
warning "react-scripts > @typescript-eslint/parser@1.6.0" has unmet peer dependency "typescript@*".
warning "react-scripts > ts-pnp@1.1.2" has unmet peer dependency "typescript@*".
warning "react-scripts > @typescript-eslint/eslint-plugin > @typescript-eslint/typescript-estree@1.6.0" has unmet peer dependency "typescript@*".
warning "react-scripts > @typescript-eslint/eslint-plugin > tsutils@3.14.0" has unmet peer dependency "typescript@>=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev".
warning "@aws-amplify/cli > amplify-util-mock > amplify-appsync-simulator > @conduitvc/mosca@2.8.3" has unmet peer dependency "leveldown@~1.4.3".
warning "@aws-amplify/cli > amplify-util-mock > amplify-appsync-simulator > @conduitvc/mosca@2.8.3" has unmet peer dependency "amqp@~0.2.4".
warning "@aws-amplify/cli > amplify-util-mock > amplify-appsync-simulator > @conduitvc/mosca@2.8.3" has unmet peer dependency "ioredis@^1.15.1".
warning "@aws-amplify/cli > amplify-util-mock > amplify-appsync-simulator > @conduitvc/mosca@2.8.3" has unmet peer dependency "mongodb@~2.1.4".
[4/4] Building fresh packages...
warning Error running install script for optional dependency: "/home/circleci/repo/node_modules/zmq: Command failed.
Exit code: 1
Command: node-gyp rebuild
Arguments: 
Directory: /home/circleci/repo/node_modules/zmq
Output:
gyp info it worked if it ends with ok
gyp info using node-gyp@3.8.0
gyp info using node@10.15.0 | linux | x64
gyp http GET https://nodejs.org/download/release/v10.15.0/node-v10.15.0-headers.tar.gz
gyp http 200 https://nodejs.org/download/release/v10.15.0/node-v10.15.0-headers.tar.gz
gyp http GET https://nodejs.org/download/release/v10.15.0/SHASUMS256.txt
gyp http 200 https://nodejs.org/download/release/v10.15.0/SHASUMS256.txt
gyp info spawn /usr/bin/python2
gyp info spawn args [ '/usr/local/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py',
gyp info spawn args   'binding.gyp',
gyp info spawn args   '-f',
gyp info spawn args   'make',
gyp info spawn args   '-I',
gyp info spawn args   '/home/circleci/repo/node_modules/zmq/build/config.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/usr/local/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/home/circleci/.node-gyp/10.15.0/include/node/common.gypi',
gyp info spawn args   '-Dlibrary=shared_library',
gyp info spawn args   '-Dvisibility=default',
gyp info spawn args   '-Dnode_root_dir=/home/circleci/.node-gyp/10.15.0',
gyp info spawn args   '-Dnode_gyp_dir=/usr/local/lib/node_modules/npm/node_modules/node-gyp',
gyp info spawn args   '-Dnode_lib_file=/home/circleci/.node-gyp/10.15.0/<(target_arch)/node.lib',
gyp info spawn args   '-Dmodule_root_dir=/home/circleci/repo/node_modules/zmq',
gyp info spawn args   '-Dnode_engine=v8',
gyp info spawn args   '--depth=.',
gyp info spawn args   '--no-parallel',
gyp info spawn args   '--generator-output',
gyp info spawn args   'build',
gyp info spawn args   '-Goutput_dir=.' ]
gyp info spawn make
gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
make: Entering directory '/home/circleci/repo/node_modules/zmq/build'
  CXX(target) Release/obj.target/zmq/binding.o
../binding.cc:28:17: fatal error: zmq.h: No such file or directory
 #include <zmq.h>
                 ^
compilation terminated.
zmq.target.mk:101: recipe for target 'Release/obj.target/zmq/binding.o' failed
make: *** [Release/obj.target/zmq/binding.o] Error 1
make: Leaving directory '/home/circleci/repo/node_modules/zmq/build'
gyp ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:262:23)
gyp ERR! stack     at ChildProcess.emit (events.js:182:13)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:240:12)
gyp ERR! System Linux 4.15.0-1043-aws
gyp ERR! command \"/usr/local/bin/node\" \"/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js\" \"rebuild\"
gyp ERR! cwd /home/circleci/repo/node_modules/zmq
gyp ERR! node -v v10.15.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok"
info This module is OPTIONAL, you can safely ignore this error
warning Error running install script for optional dependency: "/home/circleci/repo/node_modules/snappy: Command failed.
Exit code: 1
Command: ./node_modules/.bin/node-gyp rebuild
Arguments: 
Directory: /home/circleci/repo/node_modules/snappy
Output:
gyp info it worked if it ends with ok
gyp info using node-gyp@3.4.0
gyp info using node@10.15.0 | linux | x64
gyp http GET https://nodejs.org/download/release/v10.15.0/node-v10.15.0-headers.tar.gz
gyp http 200 https://nodejs.org/download/release/v10.15.0/node-v10.15.0-headers.tar.gz
gyp http GET https://nodejs.org/download/release/v10.15.0/SHASUMS256.txt
gyp http 200 https://nodejs.org/download/release/v10.15.0/SHASUMS256.txt
gyp info spawn /usr/bin/python2
gyp info spawn args [ '/home/circleci/repo/node_modules/snappy/node_modules/node-gyp/gyp/gyp_main.py',
gyp info spawn args   'binding.gyp',
gyp info spawn args   '-f',
gyp info spawn args   'make',
gyp info spawn args   '-I',
gyp info spawn args   '/home/circleci/repo/node_modules/snappy/build/config.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/home/circleci/repo/node_modules/snappy/node_modules/node-gyp/addon.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/home/circleci/.node-gyp/10.15.0/include/node/common.gypi',
gyp info spawn args   '-Dlibrary=shared_library',
gyp info spawn args   '-Dvisibility=default',
gyp info spawn args   '-Dnode_root_dir=/home/circleci/.node-gyp/10.15.0',
gyp info spawn args   '-Dnode_gyp_dir=/home/circleci/repo/node_modules/snappy/node_modules/node-gyp',
gyp info spawn args   '-Dnode_lib_file=node.lib',
gyp info spawn args   '-Dmodule_root_dir=/home/circleci/repo/node_modules/snappy',
gyp info spawn args   '--depth=.',
gyp info spawn args   '--no-parallel',
gyp info spawn args   '--generator-output',
gyp info spawn args   'build',
gyp info spawn args   '-Goutput_dir=.' ]
gyp info spawn make
gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
make: Entering directory '/home/circleci/repo/node_modules/snappy/build'
  CXX(target) Release/obj.target/snappy/deps/snappy/snappy-1.1.2/snappy-sinksource.o
  CXX(target) Release/obj.target/snappy/deps/snappy/snappy-1.1.2/snappy-stubs-internal.o
  CXX(target) Release/obj.target/snappy/deps/snappy/snappy-1.1.2/snappy.o
  AR(target) Release/obj.target/deps/snappy/snappy.a
  COPY Release/snappy.a
  CXX(target) Release/obj.target/binding/src/binding.o
In file included from ../node_modules/nan/nan.h:190:0,
                 from ../src/./binding.h:6,
                 from ../src/binding.cc:1:
../node_modules/nan/nan_maybe_43_inl.h: In function ‘Nan::Maybe<bool> Nan::ForceSet(v8::Local<v8::Object>, v8::Local<v8::Value>, v8::Local<v8::Value>, v8::PropertyAttribute)’:
../node_modules/nan/nan_maybe_43_inl.h:88:15: error: ‘class v8::Object’ has no member named ‘ForceSet’
   return obj->ForceSet(GetCurrentContext(), key, value, attribs);
               ^
In file included from ../src/./binding.h:6:0,
                 from ../src/binding.cc:1:
../node_modules/nan/nan.h: In function ‘v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*)’:
../node_modules/nan/nan.h:817:60: warning: ‘v8::Local<v8::Value> node::MakeCallback(v8::Isolate*, v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*)’ is deprecated (declared at /home/circleci/.node-gyp/10.15.0/include/node/node.h:176): Use MakeCallback(..., async_context) [-Wdeprecated-declarations]
         v8::Isolate::GetCurrent(), target, func, argc, argv);
                                                            ^
../node_modules/nan/nan.h: In function ‘v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::String>, int, v8::Local<v8::Value>*)’:
../node_modules/nan/nan.h:831:62: warning: ‘v8::Local<v8::Value> node::MakeCallback(v8::Isolate*, v8::Local<v8::Object>, v8::Local<v8::String>, int, v8::Local<v8::Value>*)’ is deprecated (declared at /home/circleci/.node-gyp/10.15.0/include/node/node.h:169): Use MakeCallback(..., async_context) [-Wdeprecated-declarations]
         v8::Isolate::GetCurrent(), target, symbol, argc, argv);
                                                              ^
../node_modules/nan/nan.h: In function ‘v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, const char*, int, v8::Local<v8::Value>*)’:
../node_modules/nan/nan.h:845:62: warning: ‘v8::Local<v8::Value> node::MakeCallback(v8::Isolate*, v8::Local<v8::Object>, const char*, int, v8::Local<v8::Value>*)’ is deprecated (declared at /home/circleci/.node-gyp/10.15.0/include/node/node.h:162): Use MakeCallback(..., async_context) [-Wdeprecated-declarations]
         v8::Isolate::GetCurrent(), target, method, argc, argv);
                                                              ^
../node_modules/nan/nan.h: In member function ‘v8::Local<v8::Value> Nan::Callback::Call_(v8::Isolate*, v8::Local<v8::Object>, int, v8::Local<v8::Value>*) const’:
../node_modules/nan/nan.h:1463:5: warning: ‘v8::Local<v8::Value> node::MakeCallback(v8::Isolate*, v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*)’ is deprecated (declared at /home/circleci/.node-gyp/10.15.0/include/node/node.h:176): Use MakeCallback(..., async_context) [-Wdeprecated-declarations]
     ));
     ^
../src/binding.cc: In function ‘Nan::NAN_METHOD_RETURN_TYPE nodesnappy::Compress(Nan::NAN_METHOD_ARGS_TYPE)’:
../src/binding.cc:115:51: warning: ‘v8::Local<v8::Object> v8::Value::ToObject() const’ is deprecated (declared at /home/circleci/.node-gyp/10.15.0/include/node/v8.h:10046): Use maybe version [-Wdeprecated-declarations]
   if (node::Buffer::HasInstance(info[0]->ToObject())) {
                                                   ^
../src/binding.cc:116:54: warning: ‘v8::Local<v8::Object> v8::Value::ToObject() const’ is deprecated (declared at /home/circleci/.node-gyp/10.15.0/include/node/v8.h:10046): Use maybe version [-Wdeprecated-declarations]
     v8::Local<v8::Object> object = info[0]->ToObject();
                                                      ^
../src/binding.cc:121:53: warning: ‘v8::String::Utf8Value::Utf8Value(v8::Local<v8::Value>)’ is deprecated (declared at /home/circleci/.node-gyp/10.15.0/include/node/v8.h:2891): Use Isolate version [-Wdeprecated-declarations]
     v8::String::Utf8Value param1(info[0]->ToString());
                                                     ^
../src/binding.cc: In function ‘Nan::NAN_METHOD_RETURN_TYPE nodesnappy::CompressSync(Nan::NAN_METHOD_ARGS_TYPE)’:
../src/binding.cc:142:51: warning: ‘v8::Local<v8::Object> v8::Value::ToObject() const’ is deprecated (declared at /home/circleci/.node-gyp/10.15.0/include/node/v8.h:10046): Use maybe version [-Wdeprecated-declarations]
   if (node::Buffer::HasInstance(info[0]->ToObject())) {
                                                   ^
../src/binding.cc:143:54: warning: ‘v8::Local<v8::Object> v8::Value::ToObject() const’ is deprecated (declared at /home/circleci/.node-gyp/10.15.0/include/node/v8.h:10046): Use maybe version [-Wdeprecated-declarations]
     v8::Local<v8::Object> object = info[0]->ToObject();
                                                      ^
../src/binding.cc:148:53: warning: ‘v8::String::Utf8Value::Utf8Value(v8::Local<v8::Value>)’ is deprecated (declared at /home/circleci/.node-gyp/10.15.0/include/node/v8.h:2891): Use Isolate version [-Wdeprecated-declarations]
     v8::String::Utf8Value param1(info[0]->ToString());
                                                     ^
../src/binding.cc: In function ‘Nan::NAN_METHOD_RETURN_TYPE nodesnappy::IsValidCompressed(Nan::NAN_METHOD_ARGS_TYPE)’:
../src/binding.cc:161:52: warning: ‘v8::Local<v8::Object> v8::Value::ToObject() const’ is deprecated (declared at /home/circleci/.node-gyp/10.15.0/include/node/v8.h:10046): Use maybe version [-Wdeprecated-declarations]
   v8::Local<v8::Object> object = info[0]->ToObject();
                                                    ^
../src/binding.cc: In function ‘Nan::NAN_METHOD_RETURN_TYPE nodesnappy::IsValidCompressedSync(Nan::NAN_METHOD_ARGS_TYPE)’:
../src/binding.cc:181:52: warning: ‘v8::Local<v8::Object> v8::Value::ToObject() const’ is deprecated (declared at /home/circleci/.node-gyp/10.15.0/include/node/v8.h:10046): Use maybe version [-Wdeprecated-declarations]
   v8::Local<v8::Object> object = info[0]->ToObject();
                                                    ^
../src/binding.cc: In function ‘Nan::NAN_METHOD_RETURN_TYPE nodesnappy::UncompressSync(Nan::NAN_METHOD_ARGS_TYPE)’:
../src/binding.cc:218:52: warning: ‘v8::Local<v8::Object> v8::Value::ToObject() const’ is deprecated (declared at /home/circleci/.node-gyp/10.15.0/include/node/v8.h:10046): Use maybe version [-Wdeprecated-declarations]
   v8::Local<v8::Object> object = info[0]->ToObject();
                                                    ^
binding.target.mk:100: recipe for target 'Release/obj.target/binding/src/binding.o' failed
make: Leaving directory '/home/circleci/repo/node_modules/snappy/build'
make: *** [Release/obj.target/binding/src/binding.o] Error 1
gyp ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/home/circleci/repo/node_modules/snappy/node_modules/node-gyp/lib/build.js:276:23)
gyp ERR! stack     at ChildProcess.emit (events.js:182:13)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:240:12)
gyp ERR! System Linux 4.15.0-1043-aws
gyp ERR! command \"/usr/local/bin/node\" \"/home/circleci/repo/node_modules/snappy/node_modules/.bin/node-gyp\" \"rebuild\"
gyp ERR! cwd /home/circleci/repo/node_modules/snappy
gyp ERR! node -v v10.15.0
gyp ERR! node-gyp -v v3.4.0
gyp ERR! not ok"
info This module is OPTIONAL, you can safely ignore this error
success Saved lockfile.
success Saved 458 new dependencies.
info Direct dependencies
└─ @aws-amplify/cli@3.7.0
info All dependencies
├─ @aws-amplify/cli@3.7.0
├─ @conduitvc/mosca@2.8.3
├─ @kamilkisiela/graphql-tools@4.0.6
├─ @types/babylon@6.16.5
├─ @types/events@3.0.0
├─ @types/fs-extra@8.0.0
├─ @types/glob@7.1.1
├─ @types/global-prefix@3.0.0
├─ @types/minimatch@3.0.3
├─ @types/ora@3.2.0
├─ @types/prettier@1.18.2
├─ abstract-leveldown@2.7.2
├─ agent-base@4.3.0
├─ agentkeepalive@3.5.2
├─ aggregate-error@3.0.0
├─ amplify-appsync-simulator@0.13.0
├─ amplify-category-analytics@1.18.0
├─ amplify-category-api@1.20.0
├─ amplify-category-hosting@1.16.0
├─ amplify-category-interactions@1.19.0
├─ amplify-category-notifications@1.17.0
├─ amplify-category-xr@1.19.0
├─ amplify-dynamodb-simulator@0.13.0
├─ amplify-frontend-android@1.22.0
├─ amplify-frontend-ios@1.22.0
├─ amplify-frontend-javascript@1.20.0
├─ amplify-graphql-docs-generator@1.18.0
├─ amplify-graphql-types-generator@1.14.0
├─ amplify-storage-simulator@0.13.0
├─ amplify-util-mock@2.7.0
├─ amplify-velocity-template@0.12.0
├─ amqp@0.2.7
├─ amqplib@0.4.2
├─ ansi-align@2.0.0
├─ ansicolors@0.3.2
├─ ansistyles@0.1.3
├─ append-transform@0.4.0
├─ archiver@2.1.1
├─ archy@1.0.0
├─ arr-filter@1.1.2
├─ array-every@0.1.2
├─ array-from@2.1.1
├─ array-intersection@0.1.2
├─ array-slice@0.2.3
├─ ascoltatori@3.2.0
├─ ast-types@0.13.2
├─ async-cache@1.1.0
├─ asyncro@3.0.0
├─ aws-appsync-codegen@0.17.5
├─ babel-core@6.26.3
├─ babel-generator@6.26.1
├─ babel-helpers@6.24.1
├─ babel-preset-jest@21.2.0
├─ babel-register@6.26.0
├─ babel-template@6.26.0
├─ babel-traverse@6.26.0
├─ babel-types@6.26.0
├─ bignumber.js@7.2.1
├─ binary@0.3.0
├─ biskviit@1.0.1
├─ bitsyntax@0.0.4
├─ bottleneck@2.16.2
├─ boxen@1.3.0
├─ brfs@1.4.4
├─ bson@1.0.9
├─ buffer-alloc-unsafe@1.1.0
├─ buffer-alloc@1.2.0
├─ buffer-crc32@0.2.13
├─ buffer-equal@0.0.1
├─ buffer-fill@1.0.0
├─ buffer-shims@1.0.0
├─ buffermaker@1.2.1
├─ buffers@0.1.1
├─ builtin-modules@1.1.1
├─ builtins@1.0.3
├─ byline@5.0.0
├─ byte-size@5.0.1
├─ bytewise-core@1.2.3
├─ bytewise@1.1.0
├─ cacache@12.0.3
├─ call-limit@1.1.1
├─ callback-stream@1.1.0
├─ capture-stack-trace@1.0.1
├─ caw@2.0.1
├─ cfn-lint@1.9.7
├─ chainsaw@0.1.0
├─ cidr-regex@2.0.10
├─ clean-stack@2.2.0
├─ cli-boxes@1.0.0
├─ cli-columns@3.1.2
├─ cli-spinners@2.2.0
├─ cli-table3@0.5.1
├─ cloudform-types@3.8.0
├─ cluster-key-slot@1.1.0
├─ cmd-shim@3.0.3
├─ colors@1.3.3
├─ columnify@1.5.4
├─ commist@1.1.0
├─ compress-commons@1.2.2
├─ config-chain@1.1.12
├─ configstore@3.1.2
├─ constant-case@2.0.0
├─ content-type-parser@1.0.2
├─ crc@3.8.0
├─ crc32-stream@2.0.0
├─ create-error-class@3.0.2
├─ cross-fetch@2.2.2
├─ crypto-random-string@1.0.0
├─ cycle@1.0.3
├─ dank-each@1.0.0
├─ dank-map@0.1.0
├─ data-uri-to-buffer@2.0.1
├─ dateformat@3.0.3
├─ decompress-response@3.3.0
├─ decompress-tar@4.1.1
├─ decompress-tarbz2@4.1.1
├─ decompress-targz@4.1.1
├─ decompress-unzip@4.0.1
├─ decompress@4.2.0
├─ deep-diff@1.0.2
├─ deepcopy@0.6.3
├─ deepmerge@4.0.0
├─ default-require-extensions@1.0.0
├─ defaults@1.0.3
├─ deferred-leveldown@1.2.2
├─ degenerator@1.0.4
├─ detect-indent@4.0.0
├─ detect-port@1.3.0
├─ dezalgo@1.0.3
├─ diff@3.5.0
├─ dot-case@2.1.1
├─ double-ended-queue@2.1.0-0
├─ download-cli@1.1.1
├─ download@6.2.5
├─ duplexer2@0.1.4
├─ editor@1.0.0
├─ ejs@2.7.1
├─ env-editor@0.4.1
├─ env-paths@1.0.0
├─ err-code@1.1.2
├─ es6-promise@4.2.8
├─ escodegen@1.12.0
├─ esm@3.2.25
├─ event-lite@0.1.2
├─ event-stream@4.0.1
├─ eventemitter2@2.2.2
├─ expand-brackets@0.1.5
├─ expand-range@1.8.2
├─ ext-list@2.2.2
├─ ext-name@5.0.0
├─ extract-zip@1.6.7
├─ eyes@0.1.8
├─ falafel@2.1.0
├─ fast-json-parse@1.0.3
├─ fast-safe-stringify@1.2.3
├─ fastfall@1.5.1
├─ fastparallel@2.3.0
├─ fastq@1.6.0
├─ fastseries@1.7.2
├─ fd-slicer@1.0.1
├─ fd@0.0.3
├─ fetch@1.1.0
├─ figlet@1.2.4
├─ file-uri-to-path@1.0.0
├─ filename-regex@2.0.1
├─ filename-reserved-regex@2.0.0
├─ filenamify@2.1.0
├─ fileset@2.0.3
├─ filter-array@0.2.0
├─ flatstr@1.0.12
├─ flexbuffer@0.0.6
├─ foreach@2.0.5
├─ from@0.1.7
├─ fs-constants@1.0.0
├─ fs-ext@0.5.0
├─ fs-vacuum@1.2.10
├─ ftp@0.3.10
├─ genfun@5.0.0
├─ gentle-fs@2.2.1
├─ get-proxy@2.1.0
├─ get-uri@2.0.3
├─ glob-all@3.1.0
├─ glob-base@0.3.0
├─ glob-stream@6.1.0
├─ global-dirs@0.1.1
├─ got@7.1.0
├─ graphql-auth-transformer@5.8.0
├─ graphql-config@2.2.1
├─ graphql-elasticsearch-transformer@3.20.0
├─ graphql-function-transformer@1.15.0
├─ graphql-http-transformer@3.18.0
├─ graphql-import@0.7.1
├─ graphql-iso-date@3.6.1
├─ graphql-key-transformer@1.15.0
├─ graphql-relational-schema-transformer@1.14.0
├─ graphql-request@1.8.2
├─ graphql-scalars@1.0.1
├─ graphql-subscriptions@1.1.0
├─ graphql-tag-pluck@0.8.4
├─ graphql-toolkit@0.5.0
├─ graphql-tools@4.0.5
├─ graphql-type-json@0.3.0
├─ graphql-versioned-transformer@3.18.0
├─ has-symbol-support-x@1.4.2
├─ has-to-string-tag-x@1.4.1
├─ header-case@1.0.1
├─ help-me@1.1.0
├─ home-or-tmp@2.0.0
├─ hosted-git-info@2.8.4
├─ http-cache-semantics@3.8.1
├─ humanize-ms@1.2.1
├─ import-lazy@2.1.0
├─ index-of@0.1.1
├─ init-package-json@1.10.3
├─ inquirer-autocomplete-prompt@1.0.1
├─ int64-buffer@0.1.10
├─ ioredis@2.5.0
├─ is-absolute@1.0.0
├─ is-arguments@1.0.4
├─ is-builtin-module@1.0.0
├─ is-cidr@3.1.0
├─ is-dotfile@1.0.3
├─ is-equal-shallow@0.1.3
├─ is-generator-function@1.0.7
├─ is-installed-globally@0.1.0
├─ is-invalid-path@0.1.0
├─ is-lower-case@1.1.3
├─ is-natural-number@4.0.1
├─ is-npm@1.0.0
├─ is-object@1.0.1
├─ is-plain-obj@1.1.0
├─ is-posix-bracket@0.1.1
├─ is-primitive@2.0.0
├─ is-redirect@1.0.0
├─ is-relative@1.0.0
├─ is-unc-path@1.0.0
├─ is-upper-case@1.1.2
├─ is-valid-path@0.1.1
├─ istanbul-api@1.3.7
├─ istanbul-lib-hook@1.2.2
├─ istanbul-lib-instrument@1.10.2
├─ istanbul-lib-source-maps@1.2.6
├─ jest-environment-node@21.2.1
├─ jsdom@9.12.0
├─ json-buffer@2.0.11
├─ jsonminify@0.4.1
├─ jsonparse@1.3.1
├─ jsonschema@1.2.4
├─ JSONStream@1.3.5
├─ jwt-decode@2.2.0
├─ kafka-node@0.5.9
├─ kerberos@0.0.24
├─ latest-version@3.1.0
├─ lazy-property@1.0.0
├─ lazystream@1.0.0
├─ level-codec@7.0.1
├─ level-errors@1.0.5
├─ level-iterator-stream@1.3.1
├─ level-post@1.0.7
├─ level-sublevel@6.6.5
├─ levelup@1.3.9
├─ libcipm@4.0.3
├─ libnpm@3.0.1
├─ libnpmconfig@1.2.1
├─ libnpmpublish@1.1.2
├─ libnpx@10.2.0
├─ libphonenumber-js@1.7.24
├─ lockfile@1.0.4
├─ lodash._baseindexof@3.1.0
├─ lodash._baseuniq@4.6.0
├─ lodash._bindcallback@3.0.1
├─ lodash._cacheindexof@3.0.2
├─ lodash._createcache@3.1.2
├─ lodash._createset@4.0.3
├─ lodash._getnative@3.9.1
├─ lodash._root@3.0.1
├─ lodash.assign@4.2.0
├─ lodash.clonedeep@4.5.0
├─ lodash.restparam@3.6.1
├─ lodash.union@4.6.0
├─ lodash.without@4.4.0
├─ log-symbols@2.2.0
├─ logdown@3.2.8
├─ long@1.1.2
├─ looper@2.0.0
├─ lower-case-first@1.0.2
├─ ltgt@1.0.2
├─ magic-string@0.22.5
├─ make-error@1.3.5
├─ make-iterator@0.1.1
├─ map-stream@0.0.7
├─ math-random@1.0.4
├─ md5-file@4.0.0
├─ meant@1.0.1
├─ mem@1.1.0
├─ memdown@1.1.2
├─ merge-graphql-schemas@1.7.0
├─ merge-options@1.0.1
├─ merge-source-map@1.0.4
├─ merge@1.2.1
├─ mimic-response@1.0.1
├─ mingo@1.3.3
├─ mongodb-core@2.1.20
├─ mongodb@2.2.36
├─ moving-average@0.1.1
├─ mqtt-connection@2.1.1
├─ mqtt-packet@3.5.1
├─ mqtt@1.14.1
├─ msgpack-lite@0.1.26
├─ msgpack5@3.6.0
├─ mysql@2.17.1
├─ nanoid@2.1.1
├─ nested-error-stacks@1.0.2
├─ netmask@1.0.6
├─ node-fetch-npm@2.0.2
├─ node-gyp@5.0.3
├─ node-notifier@5.4.3
├─ node-uuid@1.4.8
├─ node-zookeeper-client@0.2.3
├─ npm-audit-report@1.3.2
├─ npm-cache-filename@1.0.2
├─ npm-conf@1.1.3
├─ npm-install-checks@3.0.0
├─ npm-pick-manifest@3.0.2
├─ npm-user-validate@1.0.0
├─ npm@6.11.3
├─ nwmatcher@1.4.4
├─ object-inspect@1.4.1
├─ object-to-xml@2.0.0
├─ object.omit@2.0.1
├─ opener@1.5.1
├─ optional@0.1.4
├─ options@0.0.6
├─ ordered-read-streams@1.0.1
├─ os@0.1.1
├─ p-event@1.3.0
├─ pac-proxy-agent@3.0.0
├─ pac-resolver@3.0.0
├─ package-json@4.0.1
├─ pacote@9.5.8
├─ parse-glob@3.0.4
├─ parse5@1.5.1
├─ pascal-case@2.0.1
├─ path-case@2.1.1
├─ pause-stream@0.0.11
├─ pbkdf2-password@1.2.1
├─ pino@2.16.0
├─ prepend-http@1.0.4
├─ preserve@0.2.0
├─ promzard@0.3.0
├─ proto-list@1.2.4
├─ protoduck@5.0.1
├─ proxy-agent@3.1.0
├─ proxy-from-env@1.0.0
├─ pull-defer@0.2.3
├─ pull-level@2.0.4
├─ pull-live@1.0.1
├─ pull-pushable@2.2.0
├─ pull-stream@3.6.14
├─ pull-window@2.1.4
├─ qlobber-fsq@3.2.4
├─ qlobber@0.7.0
├─ qrcode-terminal@0.12.0
├─ query-string@6.8.3
├─ quick-format-unescaped@1.1.2
├─ quote-stream@1.0.2
├─ qw@1.0.1
├─ randomatic@3.1.1
├─ read-cmd-shim@1.0.4
├─ read-installed@4.0.3
├─ read-package-tree@5.3.1
├─ read@1.0.7
├─ redis-commands@1.5.0
├─ redis-parser@1.3.0
├─ reduplexer@1.1.0
├─ regex-cache@0.4.4
├─ registry-auth-token@3.4.0
├─ registry-url@3.1.0
├─ reinterval@1.1.0
├─ require_optional@1.0.1
├─ retimer@1.1.0
├─ retry@0.12.0
├─ sanitizer@0.1.3
├─ save@2.4.0
├─ seek-bzip@1.0.5
├─ semver-diff@2.1.0
├─ sentence-case@2.1.1
├─ sha@3.0.0
├─ shallow-copy@0.0.1
├─ shortid@2.2.15
├─ slide@1.1.6
├─ smart-buffer@4.0.2
├─ socks-proxy-agent@4.0.2
├─ socks@2.3.2
├─ sort-keys-length@1.0.1
├─ sort-keys@1.1.2
├─ sorted-object@2.0.1
├─ sorted-union-stream@2.1.3
├─ source-map-support@0.5.13
├─ split-on-first@1.1.0
├─ split@1.0.1
├─ sqlstring@2.3.1
├─ st@1.2.2
├─ stack-trace@0.0.10
├─ static-eval@2.0.2
├─ static-module@2.2.5
├─ steed@1.1.3
├─ stream-combiner@0.2.2
├─ stream-iterate@1.2.0
├─ stream-to-pull-stream@1.7.3
├─ strict-uri-encode@2.0.0
├─ strip-dirs@2.1.0
├─ strip-final-newline@2.0.0
├─ strip-outer@1.0.1
├─ swap-case@1.1.2
├─ tar-stream@1.6.2
├─ term-size@1.2.0
├─ test-exclude@4.2.3
├─ through2-filter@3.0.0
├─ thunkify@2.1.2
├─ tiny-relative-date@1.3.0
├─ title-case@2.1.1
├─ to-absolute-glob@2.0.2
├─ to-buffer@1.1.1
├─ traverse@0.3.9
├─ trim-repeated@1.0.0
├─ ts-node@5.0.1
├─ typescript@2.9.2
├─ typewise-core@1.2.0
├─ typewise@1.0.3
├─ typewiselite@1.0.0
├─ ultron@1.0.2
├─ umask@1.1.0
├─ unbzip2-stream@1.3.3
├─ unc-path-regex@0.1.2
├─ underscore@1.9.1
├─ unique-stream@2.3.1
├─ unique-string@1.0.0
├─ unzip-response@2.0.1
├─ update-notifier@2.5.0
├─ upper-case-first@1.1.2
├─ util-extend@1.0.3
├─ util-promisify@2.1.0
├─ valid-url@1.0.9
├─ vlq@0.2.3
├─ wait-port@0.2.2
├─ watch@0.18.0
├─ wcwidth@1.0.1
├─ websocket-stream@3.1.0
├─ when@3.6.4
├─ widest-line@2.0.1
├─ winston@2.4.4
├─ write-file-atomic@2.4.3
├─ xml-js@1.6.11
├─ xml@1.0.1
├─ yauzl@2.4.1
├─ yn@2.0.0
└─ zip-stream@1.2.0
Done in 35.17s.

David-dp- commented 5 years ago

Attila, since I posted about my problem, the engineer has been back from vacation for a couple months and upgraded our amplify version in our repo.

I'm not sure why but he renames our amplify/.config/project-config.json to amplify/.config/project-config.orig before committing it, and my understanding is that I need to change the extension back to .json if I want to use it. When I do that and then...

$ amplify publish

Current Environment: undefined

Category Resource name Operation Provider plugin

Hosting S3AndCloudFront Update awscloudformation

Api restfuldb Update awscloudformation

Auth foooooooDevWebview No Change awscloudformation

Function webviewDevCallflow No Change awscloudformation

? Are you sure you want to continue? (Y/n)

Category	Resource name	Operation	Provider plugin
Hosting	S3AndCloudFront	Update	awscloudformation
Api	restfuldb	Update	awscloudformation
Auth	foooooooDevWebview	No Change	awscloudformation
Function	webviewDevCallflow	No Change	awscloudformation

Except for the environment showing as undefined, this seems to be Working As Designed.

Do you have any comment on best practices for maintaining project-config.json in a repo shared by multiple engineers?

On Wed, Sep 18, 2019 at 1:15 PM Attila Hajdrik notifications@github.com wrote:

@David-dp- https://github.com/David-dp- could you please delete your package.lock.json or its yarn counterpart and try it that way? Also observe the changes perhaps you can spot something meaningful.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/aws-amplify/amplify-cli/issues/1644?email_source=notifications&email_token=AA5RKQ4NS677Q6ZEM56WBJLQKKD6FA5CNFSM4HW4N3F2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7BJ3TY#issuecomment-532848079, or mute the thread https://github.com/notifications/unsubscribe-auth/AA5RKQ7EOL73QBVQHBKGXP3QKKD6FANCNFSM4HW4N3FQ .

github-actions[bot] commented 3 years ago

This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs.

Looking for a help forum? We recommend joining the Amplify Community Discord server *-help channels for those types of questions.