Closed oppenheimer- closed 1 year ago
Hi @oppenheimer- , unfortunately I am not that familiar with windows. Maybe @timohubois can help out? But you seem to have fixed the line ending issue anyways. The memory issue could either be fixed by adjusting you global php.ini for the cli, or adjust the line in the package.json to be
"lint:php": "cross-env ./vendor/bin/phpcs",
Otherwise you could also disable linting to see if building actually works.
This can be done by either adjusting the package.json to
"build": "run-s --silent checkVersion lint build:production",
or running npm run build:production
.
thanks for the quick answer @domtra i tried to raise the memory to 1024M, but that errored out as well.
Not sure what i should change in that specific line as it is a fresh install.
"lint:php": "cross-env ./vendor/bin/phpcs",
npm run build:production
works like a charm though.
could it be the linter overflowing?
anways, i'm glad it works now and looking forward trying flynt more now! thanks for work guys! 😎
hey, glad it worked. i totally did not adjust the lines I sent you over. this is what I meant.
"lint:php": "cross-env ./vendor/bin/phpcs -d memory_limit=512M",
and
"build": "run-s --silent checkVersion build:production",
I can successfully "npm start", but "npm run build" fails.
I'm on windows / cmd / with node 19.6.0
there were a lot of problems in found php files:
After some research, I had to tweak "phpcs.xml.dist" and added:
But now there are memory problems
i tried to raise that in the file without much success, though
raising the memory in the php.ini to 1025M didn't help either.