Closed williamli closed 6 years ago
I can't reproduce based on the steps provided 🤔
seems like you need to create a pages dir with index.js in it for it to start compiling / deploy.
add step 2.5
mkdir pages
echo "export default () => <div>hello</div>" >> pages/index.js
Already did while trying, otherwise Next would error out.
Now-CLI: v11.1.7 NodeJS: v10.1.0 and v8.11.1 NPM: v6 OS: MacOS
This is what I get when I try to deploy to now. The code is synced to server and started to build but with errors in tar header
Deploying ~/projects/tmp/next-test under bbi Using Node.js 8.11.1 (default) https://next-test-ccnokyuyeq.now.sh [in clipboard] (sfo1) [2s] Building… ▲ npm install ✓ Using "package-lock.json" ⧗ Installing 3 main dependencies… ^
Error: Invalid tar header. Maybe the tar is corrupted or it needs to be gunzipped? at Object.exports.decode (/snapshot/ace/node_modules/tar-stream/headers.js:270:43) at Extract.onheader [as _onparse] (/snapshot/ace/node_modules/tar-stream/extract.js:120:39) at Extract._write (/snapshot/ace/node_modules/tar-stream/extract.js:243:8) at Extract._continue (/snapshot/ace/node_modules/tar-stream/extract.js:207:28) at oncontinue (/snapshot/ace/node_modules/tar-stream/extract.js:64:10) at Extract.onheader [as _onparse] (/snapshot/ace/node_modules/tar-stream/extract.js:128:7) at Extract._write (/snapshot/ace/node_modules/tar-stream/extract.js:243:8) at Extract._continue (/snapshot/ace/node_modules/tar-stream/extract.js:207:28) events.js:183 at oncontinue (/snapshot/ace/node_modules/tar-stream/extract.js:64:10) at Extract.ondrain (/snapshot/ace/node_modules/tar-stream/extract.js:84:5) throw er; // Unhandled 'error' event ▲ npm install
@timneutkens Just tried it on a new server on Ubuntu.
NodeJS: v10.1.0 and v8.11.1 NPM: v6 OS: Ubuntu NOW: v11.1.7
still seeing events.js:183 (unhandled 'error' event) followed by Invalid tar header...
Hey there, I tweaked some knobs on the backend. Can you please try once again?
@TooTallNate works fine now. no more errors.
@TooTallNate not sure if related, (I haven't changed code in my project), but now npm packages I used randomly failed during the build stage in NOW.
the app still works and get deployed on the server.
Example 1: Error: Error parsing package.json
for fsevents-1.2.3.tar
Building… ▲ npm install ✓ Using "package-lock.json" ⧗ Installing 10 main dependencies… Building "fsevents@1.2.3" remotely Building "styled-components@3.2.6" remotely Building "uglifyjs-webpack-plugin@0.4.6" remotely Building "fsevents@1.2.3" remotely Building "uglifyjs-webpack-plugin@0.4.6" remotely Building "styled-components@3.2.6" remotely Building "fsevents@1.2.3" remotely Error: Error parsing
package.json
for fsevents-1.2.3.tar at extract (/snapshot/ace/lib/extract.js:36:11) atat process._tickCallback (internal/process/next_tick.js:188:7) ▲ npm install
Example 2: Error: Error parsing package.json
for styled-components-3.2.6.tar
Synced 1 file (2.71KB) [5s]
Building…
▲ npm install
✓ Using "package-lock.json"
⧗ Installing 10 main dependencies…
Building "fsevents@1.2.3" remotely
Building "styled-components@3.2.6" remotely
Building "uglifyjs-webpack-plugin@0.4.6" remotely
Building "fsevents@1.2.3" remotely
Building "styled-components@3.2.6" remotely
Building "uglifyjs-webpack-plugin@0.4.6" remotely
Building "fsevents@1.2.3" remotely
Building "styled-components@3.2.6" remotely
Error: Error parsingpackage.json
for styled-components-3.2.6.tar
at extract (/snapshot/ace/lib/extract.js:36:11)
at
at process._tickCallback (internal/process/next_tick.js:188:7)
Building "uglifyjs-webpack-plugin@0.4.6" remotely
▲ npm install
problems went away now. no more npm building errors
@williamli @timneutkens I began seeing these errors during build step. Now version is 11.3.0, Next version is 6.1.1
> Building…
> ▲ npm install
> ✓ Using "yarn.lock"
> ⧗ Installing 24 main dependencies…
> Building "jss@9.8.7" remotely
> Building "uglifyjs-webpack-plugin@0.4.6" remotely
> Building "fsevents@1.2.4" remotely
> Building "jss@9.8.7" remotely
> Building "uglifyjs-webpack-plugin@0.4.6" remotely
> Building "fsevents@1.2.4" remotely
> Building "jss@9.8.7" remotely
> Building "uglifyjs-webpack-plugin@0.4.6" remotely
> Building "fsevents@1.2.4" remotely
> Error: Error parsing `package.json` for fsevents-1.2.4.tar
> at extract (/snapshot/ace/lib/extract.js:36:11)
> at <anonymous>
> at process._tickCallback (internal/process/next_tick.js:188:7)
> Ignoring failed optional dependency "fsevents@1.2.4"
> ▲ yarn
> yarn install v1.7.0
> [1/4] Resolving packages...
> [2/4] Fetching packages...
> info fsevents@1.2.4: The platform "linux"is incompatible with this module.
> info "fsevents@1.2.4" is an optional dependency and failed compatibility check. Excluding it from installation.
> [3/4] Linking dependencies...
> warning "@zeit/next-typescript > @babel/preset-typescript > @babel/plugin-transform-typescript@7.0.0-beta.42" has unmet peer dependency "@babel/core@7.0.0-beta.42".
> warning "@zeit/next-typescript > @babel/preset-typescript@7.0.0-beta.42" has unmet peer dependency "@babel/core@7.0.0-beta.42".
> warning "@zeit/next-typescript > @babel/preset-typescript > @babel/plugin-transform-typescript > @babel/plugin-syntax-typescript@7.0.0-beta.42" has unmet peer dependency "@babel/core@7.0.0-beta.42".
> warning " > eslint-config-airbnb@17.0.0" has incorrect peer dependency "eslint@^4.19.1".
> warning "eslint-config-airbnb > eslint-config-airbnb-base@13.0.0" has incorrect peer dependency "eslint@^4.19.1".
> [4/4] Building fresh packages...
I'm also getting the "Error: Error parsing package.json
for fsevents" on now
11.3.0
and next
6.1.1
. Fixed when I upgraded to now 11.3.1
.
Next.js version: 6.0.2
NOW
Error shows up during the build log:
Deploying ~/projects/tmp/next-test under ###
App runs fine on the server. Seems some libraries are missing on the
now
fornext
.