I am not able to start wp-env and I also don't understand the error I get. I've installed wp-env, docker and all the other things I need.
I am working on Windows 10 and my account is an administrator.
"D:\OneDrive\webseiten\wpdev\wp-content\plugins\starter" is a ready to run wp-plugin.
When I try to start wp-env, I get following error:
D:\OneDrive\webseiten\wpdev\wp-content\plugins\starter>wp-env start --update
× Error: spawn git ENOENT
at Process.ChildProcess._handle.onexit (node:internal/child_process:283:19)
at onErrorNT (node:internal/child_process:478:16)
at processTicksAndRejections (node:internal/process/task_queues:83:21)
GitError: Error: spawn git ENOENT
at Process.ChildProcess._handle.onexit (node:internal/child_process:283:19)
at onErrorNT (node:internal/child_process:478:16)
at processTicksAndRejections (node:internal/process/task_queues:83:21)
at Object.action (C:\Users\Nutzer\AppData\Roaming\npm\node_modules\#wordpress\env\node_modules\simple-git\dist\cjs\index.js:1228:25)
at PluginStore.exec (C:\Users\Nutzer\AppData\Roaming\npm\node_modules\#wordpress\env\node_modules\simple-git\dist\cjs\index.js:1263:29)
at C:\Users\Nutzer\AppData\Roaming\npm\node_modules\#wordpress\env\node_modules\simple-git\dist\cjs\index.js:1627:43
at new Promise ()
at GitExecutorChain.handleTaskData (C:\Users\Nutzer\AppData\Roaming\npm\node_modules\#wordpress\env\node_modules\simple-git\dist\cjs\index.js:1625:16)
at GitExecutorChain. (C:\Users\Nutzer\AppData\Roaming\npm\node_modules\#wordpress\env\node_modules\simple-git\dist\cjs\index.js:1609:44)
at Generator.next ()
at fulfilled (C:\Users\Nutzer\AppData\Roaming\npm\node_modules\#wordpress\env\node_modules\simple-git\dist\cjs\index.js:55:24) {
task: {
commands: [
'clone',
'--depth=1',
'--no-single-branch',
'https://github.com/WordPress/WordPress.git',
'D:\\OneDrive\\webseiten\\wp-env\\7d7d92c3d29a7ac077cdad60da98c0fd\\WordPress'
],
format: 'utf-8',
parser: [Function: parser]
}
}
The overridden WP_ENV_HOME is not the problem, I got the same error with the default WP_ENV_HOME.
Anybody could help me?
I currently have a monorepo setup with serverless and it builds alright, when I try a custom deploy script, I get the following error
DEBUG ─ Executing the template's components graph.
error:
Error: Command failed with ENOENT: node_modules/.bin/next build
spawn node_modules/.bin/next ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:268:19)
at onErrorNT (internal/child_process.js:470:16)
at processTicksAndRejections (internal/process/task_queues.js:84:21) {
errno: 'ENOENT',
code: 'ENOENT',
syscall: 'spawn node_modules/.bin/next',
path: 'node_modules/.bin/next',
spawnargs: [ 'build' ],
originalMessage: 'spawn node_modules/.bin/next ENOENT',
shortMessage: 'Command failed with ENOENT: node_modules/.bin/next build\n' +
'spawn node_modules/.bin/next ENOENT',
command: 'node_modules/.bin/next build',
escapedCommand: '"node_modules/.bin/next" build',
exitCode: undefined,
signal: undefined,
signalDescription: undefined,
stdout: '',
stderr: '',
failed: true,
timedOut: false,
isCanceled: false,
killed: false
}
4s › web › Error: Command failed with ENOENT: node_modules/.bin/next build
spawn node_modules/.bin/next ENOENT
I tried to set next.config.js with
const nextConfig = {
experimental: {
externalDir: true,
},
};
export default nextConfig;
Still the error persist.
my deploy script is "deploy": "AWS_SDK_LOAD_CONFIG=1 AWS_PROFILE=projec1 yarn components-v1 --debug"
The cloud function was working good before updating it. This is the code where the error occurs now:
return spawn('convert' ,[tempLocalFile, '-thumbnail', `${THUMB_MAX_WIDTH}x${THUMB_MAX_HEIGHT}`, tempLocalThumbFile], {capture: ['stdout', 'stderr']});
Below is the detail of the error:
generateThumbnail Error: {
Error: spawn convert ENOENT at _errnoException
(util.js:1022:11) at Process.ChildProcess._handle.onexit
(internal/child_process.js:190:19) at onErrorNT
(internal/child_process.js:372:16) at _combinedTickCallback
(internal/process/next_tick.js:138:11) at process._tickDomainCallback
(internal/process/next_tick.js:218:9)
code: 'ENOENT',
errno: 'ENOENT',
syscall: 'spawn convert',
path: 'convert',
spawnargs: [
'/tmp/images/E32NIXQKgVUxjUGDmPkr_aaaa',
'-thumbnail',
'400x220',
'/tmp/images/thumb_E32NIXQKgVUxjUGDmPkr_aaaa'
]
}
Is I'm doing something wrong or Is this the firebase cloud error?
For local development : brew install imagemagick
I'm following this tutorial on building a React app on top of WordPress, and I'm having trouble starting it.
I modified package.json file a bit and webpack.config.js` and I am getting the following error in my terminal
➜ wp-api git:(development) ✗ npm start
> wp-api#1.0.0 start /Users/myuser/Projects/wp-api
> webpack-dev-server --open
Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.
- configuration.resolve has an unknown property 'modulesDirectories'. These properties are valid:
object { alias?, aliasFields?, cachePredicate?, descriptionFiles?, enforceExtension?, enforceModuleExtension?, extensions?, fileSystem?, mainFields?, mainFiles?, moduleExtensions?, modules?, plugins?, resolver?, symlinks?, unsafeCache?, useSyncFileSystemCalls? }
- configuration.resolve.extensions[0] should not be empty.
npm ERR! Darwin 16.5.0
npm ERR! argv "/usr/local/Cellar/node/7.10.0/bin/node" "/usr/local/bin/npm" "start"
npm ERR! node v7.10.0
npm ERR! npm v4.2.0
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! wp-api#1.0.0 start: `webpack-dev-server --open`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the wp-api#1.0.0 start script 'webpack-dev-server --open'.
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 wp-api package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! webpack-dev-server --open
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs wp-api
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls wp-api
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /Users/myuser/.npm/_logs/2017-05-15T07_40_36_249Z-debug.log
The log file is
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/Cellar/node/7.10.0/bin/node',
1 verbose cli '/usr/local/bin/npm',
1 verbose cli 'start' ]
2 info using npm#4.2.0
3 info using node#v7.10.0
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle wp-api#1.0.0~prestart: wp-api#1.0.0
6 silly lifecycle wp-api#1.0.0~prestart: no script for prestart, continuing
7 info lifecycle wp-api#1.0.0~start: wp-api#1.0.0
8 verbose lifecycle wp-api#1.0.0~start: unsafe-perm in lifecycle true
9 verbose lifecycle wp-api#1.0.0~start: PATH: /usr/local/lib/node_modules/npm/bin/node-gyp-bin:/Users/myuser/Projects/wp-api/node_modules/.bin:/Users/myuser/.rbenv/shims:/Users/myuser/.rbenv/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin
10 verbose lifecycle wp-api#1.0.0~start: CWD: /Users/myuser/Projects/wp-api
11 silly lifecycle wp-api#1.0.0~start: Args: [ '-c', 'webpack-dev-server --open' ]
12 silly lifecycle wp-api#1.0.0~start: Returned: code: 1 signal: null
13 info lifecycle wp-api#1.0.0~start: Failed to exec start script
14 verbose stack Error: wp-api#1.0.0 start: `webpack-dev-server --open`
14 verbose stack Exit status 1
14 verbose stack at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/lifecycle.js:279:16)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at EventEmitter.emit (events.js:194:7)
14 verbose stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:40:14)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at ChildProcess.emit (events.js:194:7)
14 verbose stack at maybeClose (internal/child_process.js:899:16)
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
15 verbose pkgid wp-api#1.0.0
16 verbose cwd /Users/myuser/Projects/wp-api
17 error Darwin 16.5.0
18 error argv "/usr/local/Cellar/node/7.10.0/bin/node" "/usr/local/bin/npm" "start"
19 error node v7.10.0
20 error npm v4.2.0
21 error code ELIFECYCLE
22 error errno 1
23 error wp-api#1.0.0 start: `webpack-dev-server --open`
23 error Exit status 1
24 error Failed at the wp-api#1.0.0 start script 'webpack-dev-server --open'.
24 error Make sure you have the latest version of node.js and npm installed.
24 error If you do, this is most likely a problem with the wp-api package,
24 error not with npm itself.
24 error Tell the author that this fails on your system:
24 error webpack-dev-server --open
24 error You can get information on how to open an issue for this project with:
24 error npm bugs wp-api
24 error Or if that isn't available, you can get their info via:
24 error npm owner ls wp-api
24 error There is likely additional logging output above.
25 verbose exit [ 1, true ]
The package.json and webpack.config.js are:
{
"name": "wp-api",
"version": "1.0.0",
"description": "React based WordPress app",
"main": "index.js",
"dependencies": {
"alt": "^0.18.6",
"axios": "^0.15.3",
"extract-text-webpack-plugin": "^2.1.0",
"lodash": "^4.17.4",
"node-sass": "^4.5.2",
"prop-types": "^15.5.8",
"react": "^15.4.2",
"react-dom": "^15.4.2",
"react-router": "^3.0.1",
"sass-loader": "^6.0.3"
},
"devDependencies": {
"babel-core": "^6.21.0",
"babel-loader": "^6.2.10",
"babel-preset-env": "^1.4.0",
"babel-preset-es2015": "^6.18.0",
"babel-preset-react": "^6.24.1",
"css-loader": "^0.28.0",
"firebase-tools": "^3.6.1",
"html-webpack-plugin": "^2.28.0",
"react-hot-loader": "^1.3.1",
"style-loader": "^0.16.1",
"webpack": "^2.4.1",
"webpack-dev-server": "^2.4.2"
},
"scripts": {
"start": "webpack-dev-server --open",
"test": "echo \"Error: no test specified\" && exit 1"
},
"babel": {
"presets": [
"env",
"react"
]
},
"author": "dingo-d",
"license": "GPL"
}
and
var webpack = require('webpack');
var path = require('path');
var HtmlWebpackPlugin = require('html-webpack-plugin');
const ExtractTextPlugin = require('extract-text-webpack-plugin');
const outputCss = 'styles/[name].css';
var config = {
devtool: 'inline-source-map', // This will show line numbers where errors are accured in the terminal
devServer: {
historyApiFallback: true, // This will make the server understand "/some-link" routs instead of "/#/some-link"
},
entry: [
'webpack-dev-server/client?http://127.0.0.1:8080/', // Specify the local server port
'webpack/hot/only-dev-server', // Enable hot reloading
'./src/index' // This is where Webpack will be looking for the entry index.js file
],
output: {
path: path.join(__dirname, 'public'), // This is used to specify folder for producion bundle. Will not be used here, but it's a good practice to have it
filename: 'bundle.js' // Filename for production bundle
// publicPath: '/'
},
resolve: {
modulesDirectories: ['node_modules', 'src'], // Folders where Webpack is going to look for files to bundle together
extensions: ['', '.js'] // Extensions that Webpack is going to expect
},
module: {
// Loaders allow you to preprocess files as you require() or “load” them. Loaders are kind of like “tasks” in other build tools, and provide a powerful way to handle frontend build steps.
loaders: [
{
test: /\.jsx?$/, // Here we're going to use JS for react components but including JSX in case this extension is prefered
exclude: /node_modules/, // Speaks for itself
loaders: ['react-hot', 'babel?presets[]=react,presets[]=es2015'] // Modules that help with hot reloading and ES6 transcription
}
],
rules: [
{ test: /\.(js)$/, use: 'babel-loader' },
{
test: /\.scss$/,
use: ExtractTextPlugin.extract({
fallback: 'style-loader',
use: [
{
loader: 'css-loader'
},
{
loader: 'sass-loader'
}
]
})
}
]
},
plugins: [
new webpack.HotModuleReplacementPlugin(), // Hot reloading
new webpack.NoErrorsPlugin(), // Webpack will let you know if there are any errors
new HtmlWebpackPlugin({
template: 'index.html'
}),
]
}
module.exports = config;
I haven't done much projects with webpack, so my knowledge in this aspect is very limited.
What am I doing wrong? I tried deleting the node_modules folder and running npm install again, but that didn't work.
Solution to the 1st problem:
npm uninstall webpack --save-dev
npm install webpack#2.1.0-beta.22 --save-dev
Solution to the
configuration.resolve.extensions[0] should not be empty. :
Remove '' from the array
resolve: {
modulesDirectories: ['node_modules', 'src'], // Folders where Webpack is going to look for files to bundle together
extensions: ['.js'] // Extensions that Webpack is going to expect
},
Or replace it with '*'
resolve: {
modulesDirectories: ['node_modules', 'src'], // Folders where Webpack is going to look for files to bundle together
extensions: ['*','.js'] // Extensions that Webpack is going to expect
},
I've cloned the react-native-hackathon-starter repo, wrote my own little app and tried to build an apk for debug using gradle assembleDebug, but I get this exception:
path\to\project\android\build\intermediates\exploded-aar\com.google.android.gms\play-services-base\10.2.1\res\drawable\common_google_signin_btn_icon_dark_normal.xml:3:29-91 : No resource found that matches the given name (at 'drawable' with value '#drawable/common_google_signin_btn_icon_dark_normal_background').
path\to\project\android\build\intermediates\exploded-aar\com.google.android.gms\play-services-base\10.2.1\res\drawable\common_google_signin_btn_icon_light_normal.xml:3:29-92 : No resource found that matches the given name (at 'drawable' with value '#drawable/common_google_signin_btn_icon_light_normal_background').
path\to\project\android\build\intermediates\exploded-aar\com.google.android.gms\play-services-base\10.2.1\res\drawable\common_google_signin_btn_text_dark_normal.xml:3:29-91 : No resource found that matches the given name (at 'drawable' with value '#drawable/common_google_signin_btn_text_dark_normal_background').
path\to\project\android\build\intermediates\exploded-aar\com.google.android.gms\play-services-base\10.2.1\res\drawable\common_google_signin_btn_text_light_normal.xml:3:29-92 : No resource found that matches the given name (at 'drawable' with value '#drawable/common_google_signin_btn_text_light_normal_background').
FAILED
FAILURE: Build failed with an exception.
What went wrong:
Execution failed for task ':react-native-firestack:processReleaseResources'.
com.android.ide.common.process.ProcessException: org.gradle.process.internal.ExecException: Process 'command 'C:\Users\my_user\AppData\Local\Android\android-sdk\build-tools\23.0.1\aapt.exe'' finished with non-zero exit value 1
Try:
Run with --info or --debug option to get more log output.
Exception is:
org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':react-native-firestack:processReleaseResources'.
From what I can tell, it's missing some graphical resources. I've tried gradlew clean before assemble, it still doesn't fix the issue.
Someone else has the same issue as me.
My package.json:
{
"name": "HackathonStarter",
"version": "0.0.2",
"private": true,
"scripts": {
"start": "node node_modules/react-native/local-cli/cli.js start",
"test": "jest"
},
"dependencies": {
"firebase": "^3.6.7",
"native-base": "^2.1.0",
"react-addons-update": "^15.4.2",
"react-native-easy-grid": "^0.1.8",
"react-native-firestack": "^2.3.9",
"react-native-router-flux": "^3.37.0",
"react-native-svg": "^5.1.7",
"redux-thunk": "^2.2.0",
"jest-react-native": "^18.0.0",
"lodash": "^4.17.4",
"react": "~15.5.4",
"react-native": "0.43.4",
"react-native-elements": "^0.11.2",
"react-native-vector-icons": "^4.0.0",
"react-redux": "^5.0.1",
"redux": "^3.6.0"
},
"devDependencies": {
"babel-jest": "19.0.0",
"babel-preset-react-native": "1.9.1",
"jest": "19.0.2",
"react-test-renderer": "~15.5.4"
},
"jest": {
"preset": "react-native"
}
}
Does anyone have any idea how to fix this?
After deleting the node_modules folder, doing another npm install, removing node_modules/react-native-router-flux/react-native and editing out
compile 'com.google.android.gms:play-services-base:+
from node_modules/react-native-firestack/android/build.gradle, because it was causing interference with the gms dependency in my root build.gradle, I was able to do a gradlew assembleDebug and assembleRelease.
I think there was a problem with the firestack package, not bundling assets together correctly or whatever. All good now.