axe312ger / metalsmith-sharp Goto Github PK
View Code? Open in Web Editor NEWFlexible sharp integration for Metalsmith.
Flexible sharp integration for Metalsmith.
@axe312ger would you mind merging #next into #master? It contains additions I've made back then and it would be great to use them with the latest changes on #master of this plugin.
Thanks a lot in advance.
5.2.1
to 5.3.0
.This version is covered by your current version range and after updating it in your project the build failed.
eslint-plugin-babel is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Branch | Build failing 🚨 |
---|---|
Dependency | nyc |
Current Version | 10.1.2 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As nyc is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
The new version differs by 6 commits .
455619f
chore(release): 10.2.0
95cc09a
feat: upgrade to version of yargs with extend support (#541)
43535f9
chore: explicit update of istanbuljs dependencies (#535)
98ebdff
feat: allow babel cache to be enabled (#517)
50adde4
feat: exclude the coverage/ folder by default 🚀 (#502)
6a59834
chore(package): update tap to version 10.0.0 (#507)
See the full diff.
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
Branch | Build failing 🚨 |
---|---|
Dependency | debug |
Current Version | 2.6.1 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
As debug is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪
The new version differs by 7 commits .
017a9d6
release 2.6.2
23bc780
fix DEBUG_MAX_ARRAY_LENGTH
065cbfb
Add backers and sponsors from Open Collective (#422)
918d686
Revert "add Slackin invite badge"
f46d671
add Slackin invite badge
580a7a1
changed slackin url
9f33c9a
added slackin
See the full diff.
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
Branch | Build failing 🚨 |
---|---|
Dependency | eslint |
Current Version | 3.15.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As eslint is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
sourceCode.getTokenAfter
shouldn't skip tokens after comments (#8055) (Toru Nagashima)The new version differs by 31 commits .
3c26a59
3.16.0
5bdb960
Build: package.json and changelog update for 3.16.0
d89d0b4
Update: fix quotes false negative for string literals as template tags (#8107)
21be366
Chore: Ensuring eslint:recommended rules are sorted. (#8106)
360dbe4
Update: Improve error message when extend config missing (fixes #6115) (#8100)
f62a724
Chore: use updated token iterator methods (#8103)
daf6f26
Fix: check output in RuleTester when errors is a number (fixes #7640) (#8097)
cfb65c5
Update: make no-lone-blocks report blocks in switch cases (fixes #8047) (#8062)
290fb1f
Update: Add includeComments to getTokenByRangeStart (fixes #8068) (#8069)
ff066dc
Chore: Incorrect source code test text (#8096)
14d146d
Docs: Clarify --ext only works with directories (fixes #7939) (#8095)
013a454
Docs: Add TSC meeting quorum requirement (#8086)
7516303
Fix: sourceCode.getTokenAfter
shouldn't skip tokens after comments (#8055)
c53e034
Fix: unicode-bom fixer insert BOM in appropriate location (fixes #8083) (#8084)
55ac302
Chore: fix the timing to define rules for tests (#8082)
There are 31 commits in total. See the full diff.
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
Branch | Build failing 🚨 |
---|---|
Dependency | cross-env |
Current Version | 3.1.4 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As cross-env is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
<a name"3.2.0">
The new version differs by 4 commits .
dad00c4
feat(revamp): revamp the entire lib (backward compatible) (#63)
e33a85c
docs(README): Add doc for cross-var. (#58)
5e590ec
docs(README): added how to use cross-env to run npm sub-scripts (#53)
afdb2de
docs(README): mention Bash on Windows (#49)
See the full diff.
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
I have an issue similar to lovell/sharp#729 where SVGs get rasterized at load and then scaling them up with the resize
method greatly reduces quality.
The suggestion in that issue is to specify a high density in the constructor (docs: https://sharp.pixelplumbing.com/api-constructor), but it looks like passing the options
parameter isn't supported right now:
Line 27 in 9c57422
Hoping that can get added as option to the in some way, at the same level as say src
or methods
, and maybe the value could either be an object or a function that returns an object, similar to args
.
Thanks!
Branch | Build failing 🚨 |
---|---|
Dependency | babel-eslint |
Current Version | 7.1.1 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As babel-eslint is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
Main change is just an option to disable the codeframe (added in v7.1.1) for html output and more (thanks to @Couto).
{ "parser": "babel-eslint", "parserOptions": { "codeFrame": false }, "extends": "eslint:recommended" }
lodash
instead of lodash.pickby
. (#435) (wtgtybhertgeghgtwtg)*
" (#426) (Henry Zhu)*
(#421) (Henry Zhu)The new version differs by 17 commits .
4db4db5
7.2.0
4499412
Use lodash
instead of lodash.pickby
. (#435)
a2c3b30
[flow] Process polymorphic type bounds on functions (#444)
515adef
Add option to disable code frame. (#446)
ce66e73
Merge pull request #447 from kaicataldo/clean-up-eslint
b49ab20
Updates ESLint version/remove unnecessary config
702d6b8
Remove broken ESLint tests
6b4c4ca
Upgrade outdated dependencies
bdeb86f
remove deprecated rule examples [skip ci]
52b4a13
update readme [skip ci]
0e5aca3
chore(package): update eslint-config-babel to version 6.0.0 (#433)
781dc77
Update to use Node 4 features (#425)
265d219
chore(package): update eslint-config-babel to version 4.0.0 (#430)
e6af5c5
add badges [skip ci]
a91a9d0
Revert "use *
" (#426)
There are 17 commits in total. See the full diff.
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
Running npm install metalsmith-sharp
from Command Prompt fails.
The cause appears to be that the installation script is trying to build Sharp v0.21.3 from source, instead of using a pre-compiled release.
Log:
C:\Ebackup\Blog\debigare-netlify-metalsmith>npm install metalsmith-sharp
(node:6472) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 drain listeners added to [TLSSocket]. Use emitter.setMaxListeners() to increase limit
> [email protected] install C:\Ebackup\Blog\debigare-netlify-metalsmith\node_modules\sharp
> (node install/libvips && node install/dll-copy && prebuild-install) || (node-gyp rebuild && node install/dll-copy)
info sharp Downloading https://github.com/lovell/sharp-libvips/releases/download/v8.7.0/libvips-8.7.0-win32-x64.tar.gz
info sharp Creating C:\Ebackup\Blog\debigare-netlify-metalsmith\node_modules\sharp\build\Release
info sharp Copying DLLs from C:\Ebackup\Blog\debigare-netlify-metalsmith\node_modules\sharp\vendor\lib to C:\Ebackup\Blog\debigare-netlify-metalsmith\node_modules\sharp\build\Release
prebuild-install WARN install No prebuilt binaries found (target=12.9.0 runtime=node arch=x64 libc= platform=win32)
C:\Ebackup\Blog\debigare-netlify-metalsmith\node_modules\sharp>if not defined npm_config_node_gyp (node "C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild) else (node "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" rebuild )
gyp ERR! find Python
gyp ERR! find Python Python is not set from command line or npm configuration
gyp ERR! find Python Python is not set from environment variable PYTHON
gyp ERR! find Python checking if "python" can be used
gyp ERR! find Python - "python" is not in PATH or produced an error
gyp ERR! find Python checking if "python2" can be used
gyp ERR! find Python - "python2" is not in PATH or produced an error
gyp ERR! find Python checking if the py launcher can be used to find Python 2
gyp ERR! find Python - "py.exe" is not in PATH or produced an error
gyp ERR! find Python checking if Python is C:\Python27\python.exe
gyp ERR! find Python - "C:\Python27\python.exe" could not be run
gyp ERR! find Python checking if Python is C:\Python37\python.exe
gyp ERR! find Python - "C:\Python37\python.exe" could not be run
gyp ERR! find Python
gyp ERR! find Python **********************************************************
gyp ERR! find Python You need to install the latest version of Python 2.7.
gyp ERR! find Python Node-gyp should be able to find and use Python. If not,
gyp ERR! find Python you can try one of the following options:
gyp ERR! find Python - Use the switch --python="C:\Path\To\python.exe"
gyp ERR! find Python (accepted by both node-gyp and npm)
gyp ERR! find Python - Set the environment variable PYTHON
gyp ERR! find Python - Set the npm configuration variable python:
gyp ERR! find Python npm config set python "C:\Path\To\python.exe"
gyp ERR! find Python For more information consult the documentation at:
gyp ERR! find Python https://github.com/nodejs/node-gyp#installation
gyp ERR! find Python **********************************************************
gyp ERR! find Python
gyp ERR! configure error
gyp ERR! stack Error: Could not find any Python installation to use
gyp ERR! stack at PythonFinder.fail (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-python.js:303:47)
gyp ERR! stack at PythonFinder.runChecks (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-python.js:132:21)
gyp ERR! stack at PythonFinder.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-python.js:221:16)
gyp ERR! stack at PythonFinder.execFileCallback (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-python.js:267:16)
gyp ERR! stack at exithandler (child_process.js:302:5)
gyp ERR! stack at ChildProcess.errorhandler (child_process.js:314:5)
gyp ERR! stack at ChildProcess.emit (events.js:209:13)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:270:12)
gyp ERR! stack at onErrorNT (internal/child_process.js:456:16)
gyp ERR! stack at processTicksAndRejections (internal/process/task_queues.js:77:11)
gyp ERR! System Windows_NT 6.1.7601
gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
gyp ERR! cwd C:\Ebackup\Blog\debigare-netlify-metalsmith\node_modules\sharp
gyp ERR! node -v v12.9.0
gyp ERR! node-gyp -v v5.0.3
gyp ERR! not ok
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] install: `(node install/libvips && node install/dll-copy && prebuild-install) || (node-gyp rebuild && node install/dll-copy)`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Owner\AppData\Roaming\npm-cache\_logs\2019-09-08T21_27_15_143Z-debug.log
Branch | Build failing 🚨 |
---|---|
Dependency | babel-cli |
Current Version | 6.22.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As babel-cli is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
The link to »minimatch features« in Readme > Options > src is broken and currently pointing to https://github.com/axe312ger/metalsmith-sharp/blob/master
.
also extend readme demonstrate the correct loading of the module
The Node 4 version sits in a different directory than documented in the Readme.
Readme:
metalsmith-sharp/dist/node-4
Actual:
metalsmith-sharp/dist/node4
Branch | Build failing 🚨 |
---|---|
Dependency | eslint-plugin-babel |
Current Version | 4.0.1 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As eslint-plugin-babel is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
babel/semi
: Includes class properties (🛠 ) There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
Branch | Build failing 🚨 |
---|---|
Dependency | debug |
Current Version | 2.3.3 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
As debug is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪
The new version differs by 7 commits .
b82d4e6
release 2.4.0
41002f1
Update bower.json (#342)
e58d54b
Node: configurable util.inspect()
options (#327)
00f3046
Node: %O
(big O) pretty-prints the object (#322)
bd9faa1
allow colours in workers (#335)
501521f
Use same color for same namespace. (#338)
e2a1955
Revert "handle regex special characters"
See the full diff.
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
15.10.2
to 15.10.3
.This version is covered by your current version range and after updating it in your project the build failed.
semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
The new version differs by 6 commits.
0578c8b
fix: do not log outated branch error for missing permission cases
e291101
docs: add section existing tags in configuration docs
8853922
docs: add troubleshooting section for reference already exists
Git error
d45861b
docs: clarify the "npm missing permission" troubleshooting section
2ba0b81
docs: remove troubleshooting section related to legacy error messages
e93a663
docs: fix markdown link in configuration docs
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Branch | Build failing 🚨 |
---|---|
Dependency | eslint-plugin-promise |
Current Version | 3.4.2 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As eslint-plugin-promise is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
The new version differs by 5 commits .
cf01cd1
3.5.0
37fb563
Merge pull request #57 from ChristianMurphy/issue-53
df7bfef
Add recommended configuration to README documentation
dc4c033
Add recommended configuration
ce7a555
Updated changelog
See the full diff.
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
See: https://circleci.com/docs/how-cache-works/
Just add a second one for the node4 modules, so they can be cached also. Docs are not clear enough if this will work, lets find out.
The Readme seems to be wrong about the moveFile
option. It reads:
Set this option to false to delete the input file.
Setting moveFile
to true
actually removes the original file.
I find the terminology of moveFile
also a bit confusing. Maybe deleteInputFile
would fit better?
Branch | Build failing 🚨 |
---|---|
Dependency | babel-core |
Current Version | 6.23.1 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As babel-core is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
Branch | Build failing 🚨 |
---|---|
Dependency | eslint-plugin-standard |
Current Version | 2.1.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As eslint-plugin-standard is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
The new version differs by 4 commits .
ba689f0
2.1.1
98b51e8
updated changelog
c9a1dfb
Merge pull request #20 from xjamundx/no-callback-literal-false
84dee91
Don't allow false
in "no-callback-literal"
See the full diff.
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
Branch | Build failing 🚨 |
---|---|
Dependency | babel-core |
Current Version | 6.22.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As babel-core is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
Branch | Build failing 🚨 |
---|---|
Dependency | ava |
Current Version | 0.18.1 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As ava is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
Many bug fixes for snapshot testing, magic assert, and the type definitions: v0.18.1...v0.18.2
The new version differs by 26 commits .
98dded5
0.18.2
7cba283
Speed up flow check (#1241)
d47c5c8
Document that deepEqual() uses lodash.isequal
2ff56ce
Don't call toJSON() when formatting values
795f097
@ava/pretty-format@^1.1.0
9cea60d
Ensure test run failures crash worker (#1265)
f3b60f4
Code excerpt fixes (#1271)
8d6f9bc
Fix typo in babelrc docs
3d75834
Remove Notes section from babelrc documentation
4f87059
Ensure watcher rethrows logger errors
da68f29
Simplify failure output - fixes #1072 (#1234)
2c683b9
Clean up API tests (#1258)
8a8669c
Generate HTML coverage reports (#1259)
87ea70f
Ensure TAP reporter test does not write to stderr (#1240)
09a4765
Avoid helper compilation during API tests
There are 26 commits in total. See the full diff.
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
metalsmith-sharp
uses sharp@^0.21.1
:
Line 73 in edb0141
[email protected]
only goes up to NODE_MODULE_VERSION 67: https://github.com/lovell/sharp/releases/tag/v0.21.3
Which ends up causing:
$ docker run node:12.13.0 npm install [email protected]
npm WARN deprecated [email protected]: CoffeeScript on NPM has moved to "coffeescript" (no hyphen)
> [email protected] install /node_modules/sharp
> (node install/libvips && node install/dll-copy && prebuild-install) || (node-gyp rebuild && node install/dll-copy)
info sharp Downloading https://github.com/lovell/sharp-libvips/releases/download/v8.7.0/libvips-8.7.0-linux-x64.tar.gz
prebuild-install WARN install No prebuilt binaries found (target=12.13.0 runtime=node arch=x64 libc= platform=linux)
make: Entering directory '/node_modules/sharp/build'
TOUCH Release/obj.target/libvips-cpp.stamp
CXX(target) Release/obj.target/sharp/src/common.o
In file included from ../src/common.cc:27:0:
../src/common.h:78:16: error: 'Handle' is not a member of 'v8'
bool HasAttr(v8::Handle<v8::Object> obj, std::string attr);
^~
../src/common.h:78:37: error: expected primary-expression before '>' token
bool HasAttr(v8::Handle<v8::Object> obj, std::string attr);
^
../src/common.h:78:39: error: 'obj' was not declared in this scope
bool HasAttr(v8::Handle<v8::Object> obj, std::string attr);
^~~
../src/common.h:78:56: error: expected primary-expression before 'attr'
bool HasAttr(v8::Handle<v8::Object> obj, std::string attr);
^~~~
../src/common.h:78:60: error: expression list treated as compound expression in initializer [-fpermissive]
bool HasAttr(v8::Handle<v8::Object> obj, std::string attr);
^
../src/common.h:79:25: error: 'Handle' is not a member of 'v8'
std::string AttrAsStr(v8::Handle<v8::Object> obj, std::string attr);
^~
../src/common.h:79:46: error: expected primary-expression before '>' token
std::string AttrAsStr(v8::Handle<v8::Object> obj, std::string attr);
^
../src/common.h:79:48: error: 'obj' was not declared in this scope
std::string AttrAsStr(v8::Handle<v8::Object> obj, std::string attr);
^~~
../src/common.h:79:65: error: expected primary-expression before 'attr'
std::string AttrAsStr(v8::Handle<v8::Object> obj, std::string attr);
^~~~
../src/common.h:80:34: error: 'Handle' is not a member of 'v8'
std::vector<double> AttrAsRgba(v8::Handle<v8::Object> obj, std::string attr);
^~
../src/common.h:80:55: error: expected primary-expression before '>' token
std::vector<double> AttrAsRgba(v8::Handle<v8::Object> obj, std::string attr);
^
../src/common.h:80:57: error: 'obj' was not declared in this scope
std::vector<double> AttrAsRgba(v8::Handle<v8::Object> obj, std::string attr);
^~~
../src/common.h:80:74: error: expected primary-expression before 'attr'
std::vector<double> AttrAsRgba(v8::Handle<v8::Object> obj, std::string attr);
^~~~
../src/common.h:81:44: error: 'Handle' is not a member of 'v8'
template<typename T> v8::Local<T> AttrAs(v8::Handle<v8::Object> obj, std::string attr) {
^~
../src/common.h:81:65: error: expected primary-expression before '>' token
template<typename T> v8::Local<T> AttrAs(v8::Handle<v8::Object> obj, std::string attr) {
^
../src/common.h:81:67: error: 'obj' was not declared in this scope
template<typename T> v8::Local<T> AttrAs(v8::Handle<v8::Object> obj, std::string attr) {
^~~
../src/common.h:81:84: error: expected primary-expression before 'attr'
template<typename T> v8::Local<T> AttrAs(v8::Handle<v8::Object> obj, std::string attr) {
^~~~
../src/common.h:81:37: warning: variable templates only available with -std=c++14 or -std=gnu++14
template<typename T> v8::Local<T> AttrAs(v8::Handle<v8::Object> obj, std::string attr) {
^~~~~~
../src/common.h:81:90: error: expected ';' before '{' token
template<typename T> v8::Local<T> AttrAs(v8::Handle<v8::Object> obj, std::string attr) {
^
../src/common.h:84:33: error: 'Handle' is not a member of 'v8'
template<typename T> T AttrTo(v8::Handle<v8::Object> obj, std::string attr) {
^~
../src/common.h:84:54: error: expected primary-expression before '>' token
template<typename T> T AttrTo(v8::Handle<v8::Object> obj, std::string attr) {
^
../src/common.h:84:56: error: 'obj' was not declared in this scope
template<typename T> T AttrTo(v8::Handle<v8::Object> obj, std::string attr) {
^~~
../src/common.h:84:73: error: expected primary-expression before 'attr'
template<typename T> T AttrTo(v8::Handle<v8::Object> obj, std::string attr) {
^~~~
../src/common.h:84:26: warning: variable templates only available with -std=c++14 or -std=gnu++14
template<typename T> T AttrTo(v8::Handle<v8::Object> obj, std::string attr) {
^~~~~~
../src/common.h:84:79: error: expected ';' before '{' token
template<typename T> T AttrTo(v8::Handle<v8::Object> obj, std::string attr) {
^
../src/common.h:87:33: error: 'Handle' is not a member of 'v8'
template<typename T> T AttrTo(v8::Handle<v8::Object> obj, int attr) {
^~
../src/common.h:87:54: error: expected primary-expression before '>' token
template<typename T> T AttrTo(v8::Handle<v8::Object> obj, int attr) {
^
../src/common.h:87:56: error: 'obj' was not declared in this scope
template<typename T> T AttrTo(v8::Handle<v8::Object> obj, int attr) {
^~~
../src/common.h:87:61: error: expected primary-expression before 'int'
template<typename T> T AttrTo(v8::Handle<v8::Object> obj, int attr) {
^~~
../src/common.h:84:26: warning: variable templates only available with -std=c++14 or -std=gnu++14
template<typename T> T AttrTo(v8::Handle<v8::Object> obj, std::string attr) {
^~~~~~
../src/common.h:87:71: error: expected ';' before '{' token
template<typename T> T AttrTo(v8::Handle<v8::Object> obj, int attr) {
^
../src/common.h:93:5: error: 'Handle' is not a member of 'v8'
v8::Handle<v8::Object> input, std::vector<v8::Local<v8::Object>> &buffersToPersist);
^~
../src/common.h:93:26: error: expected primary-expression before '>' token
v8::Handle<v8::Object> input, std::vector<v8::Local<v8::Object>> &buffersToPersist);
^
../src/common.h:93:28: error: 'input' was not declared in this scope
v8::Handle<v8::Object> input, std::vector<v8::Local<v8::Object>> &buffersToPersist);
^~~~~
../src/common.h:93:70: error: expected primary-expression before '&' token
v8::Handle<v8::Object> input, std::vector<v8::Local<v8::Object>> &buffersToPersist);
^
../src/common.h:93:71: error: 'buffersToPersist' was not declared in this scope
v8::Handle<v8::Object> input, std::vector<v8::Local<v8::Object>> &buffersToPersist);
^~~~~~~~~~~~~~~~
../src/common.h:93:87: error: expression list treated as compound expression in initializer [-fpermissive]
v8::Handle<v8::Object> input, std::vector<v8::Local<v8::Object>> &buffersToPersist);
^
../src/common.cc:34:20: error: redefinition of 'bool sharp::HasAttr'
bool HasAttr(v8::Handle<v8::Object> obj, std::string attr) {
^~~~~~
In file included from ../src/common.cc:27:0:
../src/common.h:78:8: note: 'bool sharp::HasAttr' previously defined here
bool HasAttr(v8::Handle<v8::Object> obj, std::string attr);
^~~~~~~
../src/common.cc:34:16: error: 'Handle' is not a member of 'v8'
bool HasAttr(v8::Handle<v8::Object> obj, std::string attr) {
^~
../src/common.cc:34:37: error: expected primary-expression before '>' token
bool HasAttr(v8::Handle<v8::Object> obj, std::string attr) {
^
../src/common.cc:34:39: error: 'obj' was not declared in this scope
bool HasAttr(v8::Handle<v8::Object> obj, std::string attr) {
^~~
../src/common.cc:34:56: error: expected primary-expression before 'attr'
bool HasAttr(v8::Handle<v8::Object> obj, std::string attr) {
^~~~
../src/common.cc:37:29: error: redefinition of 'std::string sharp::AttrAsStr'
std::string AttrAsStr(v8::Handle<v8::Object> obj, std::string attr) {
^~~~~~
In file included from ../src/common.cc:27:0:
../src/common.h:79:15: note: 'std::string sharp::AttrAsStr' previously declared here
std::string AttrAsStr(v8::Handle<v8::Object> obj, std::string attr);
^~~~~~~~~
../src/common.cc:37:25: error: 'Handle' is not a member of 'v8'
std::string AttrAsStr(v8::Handle<v8::Object> obj, std::string attr) {
^~
../src/common.cc:37:46: error: expected primary-expression before '>' token
std::string AttrAsStr(v8::Handle<v8::Object> obj, std::string attr) {
^
../src/common.cc:37:48: error: 'obj' was not declared in this scope
std::string AttrAsStr(v8::Handle<v8::Object> obj, std::string attr) {
^~~
../src/common.cc:37:65: error: expected primary-expression before 'attr'
std::string AttrAsStr(v8::Handle<v8::Object> obj, std::string attr) {
^~~~
../src/common.cc:40:38: error: redefinition of 'std::vector<double> sharp::AttrAsRgba'
std::vector<double> AttrAsRgba(v8::Handle<v8::Object> obj, std::string attr) {
^~~~~~
In file included from ../src/common.cc:27:0:
../src/common.h:80:23: note: 'std::vector<double> sharp::AttrAsRgba' previously declared here
std::vector<double> AttrAsRgba(v8::Handle<v8::Object> obj, std::string attr);
^~~~~~~~~~
../src/common.cc:40:34: error: 'Handle' is not a member of 'v8'
std::vector<double> AttrAsRgba(v8::Handle<v8::Object> obj, std::string attr) {
^~
../src/common.cc:40:55: error: expected primary-expression before '>' token
std::vector<double> AttrAsRgba(v8::Handle<v8::Object> obj, std::string attr) {
^
../src/common.cc:40:57: error: 'obj' was not declared in this scope
std::vector<double> AttrAsRgba(v8::Handle<v8::Object> obj, std::string attr) {
^~~
../src/common.cc:40:74: error: expected primary-expression before 'attr'
std::vector<double> AttrAsRgba(v8::Handle<v8::Object> obj, std::string attr) {
^~~~
../src/common.cc:654:1: error: expected '}' at end of input
} // namespace sharp
^
cc1plus: warning: unrecognized command line option '-Wno-cast-function-type'
make: *** [Release/obj.target/sharp/src/common.o] Error 1
sharp.target.mk:136: recipe for target 'Release/obj.target/sharp/src/common.o' failed
make: Leaving directory '/node_modules/sharp/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:194:23)
gyp ERR! stack at ChildProcess.emit (events.js:210:5)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:272:12)
gyp ERR! System Linux 4.9.184-linuxkit
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 /node_modules/sharp
gyp ERR! node -v v12.13.0
gyp ERR! node-gyp -v v5.0.5
gyp ERR! not ok
npm WARN enoent ENOENT: no such file or directory, open '/package.json'
npm WARN !invalid#1 No description
npm WARN !invalid#1 No repository field.
npm WARN !invalid#1 No README data
npm WARN !invalid#1 No license field.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] install: `(node install/libvips && node install/dll-copy && prebuild-install) || (node-gyp rebuild && node install/dll-copy)`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2019-11-04T18_57_06_715Z-debug.log
This wasn't a problem for me until the Node LTS changed from v10 to v12 on Oct 21: https://nodejs.org/en/about/releases/
I'm trying without success to use the resize method with custom options. This version is just ignored:
{
"name": "resize",
"args": [200,200,{
"fit":"inside",
"withoutEnlargement":true
}
]
}
And with an object in args I receive the following error:
Expected integer between 1 and 16383 for width but received [object Object] of type object
{
"name": "resize",
"args": [
{
"width":200,
"height":200,
"fit":"inside",
"withoutEnlargement":true
}
]
}
So it seems sharp doesn't accept an object, however, according to the sharp documentation, this should be acceptable set of options. How can I set these options so the images are no wider and no higher than 200 pixels, without cropping and no larger than the input image?
Looking into your code, it should work so maybe I'm missing something obvious...
Thanks for your help.
On Windows (process.platform === 'win32'
) the path separator is \
, not /
as used here:
metalsmith-sharp/dist/index.js
Line 48 in 9c57422
Is there an easy way to create two different versions, for example one with the specific target resolution and one with the same resolution doubled, named respectively [email protected]
and [email protected]
?
I gave it a quick shot, and I ended up with:
[email protected]
image@[email protected]
and [email protected]
.
I think this is quite a common use case.
Branch | Build failing 🚨 |
---|---|
Dependency | eslint-plugin-standard |
Current Version | 2.1.1 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As eslint-plugin-standard is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
Branch | Build failing 🚨 |
---|---|
Dependency | eslint-plugin-promise |
Current Version | 3.4.1 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As eslint-plugin-promise is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
The new version differs by 5 commits .
1aba2bd
3.4.2
7ee911a
Merge pull request #56 from geoffdutton/conditional-returns
54483e1
Updated changelog
360fb8b
scope to .then function call
b84874f
perhaps a solution?
See the full diff.
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
I've got a problem excluding files when doing multiple manipulations in one call:
There is set A of images matched by a glob-pattern which I would like to manipulate in a certain way.
Then there is set B matched by a different glob-pattern, which I would like to manipulate differently, but the latter is overlapping with the first one.
How can I efficiently exclude set A from set B?
Ideally, I would just like to pass the first glob-pattern as exclude pattern in the second run, without having to merge it into a single glob pattern.
In node-glob, e.g. there is an ignore
option which excepts arrays as well, which seems to be what I'm looking for:
Add a pattern or an array of glob patterns to exclude matches.
Thanks!
Branch | Build failing 🚨 |
---|---|
Dependency | sharp |
Current Version | 0.20.6 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
sharp is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Branch | Build failing 🚨 |
---|---|
Dependency | cross-env |
Current Version | 3.1.3 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As cross-env is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
The new version differs by 2 commits .
b4a0063
fix: Enforce minimum Node.js version requirement using 'engines' attribute package.json (#48)
25f7b5f
chore(git): add .gitattributes file
See the full diff.
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
master
branch failed. 🚨I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master
branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here is some links that can help you:
If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.
The npm token configured in the NPM_TOKEN
environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/
.
If you are using Two-Factor Authentication, make configure the auth-only
level is supported. semantic-release cannot publish with the default auth-and-writes
level.
Please make sure to set the NPM_TOKEN
environment variable in your CI with the exact value of the npm token.
Good luck with your project ✨
Your semantic-release bot 📦🚀
2.0.1
to 2.0.2
.This version is covered by your current version range and after updating it in your project the build failed.
condition-circle is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
The new version differs by 3 commits.
0da0675
chore: upgrade to circle v2 for #14
a2f0716
fix: relax sem-rel dependency for #13
1d8a65b
chore(package): relax the sem-rel peer dependency (#13)
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Branch | Build failing 🚨 |
---|---|
Dependency | lodash |
Current Version | 4.17.3 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
As lodash is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
4.1.0
to 4.1.1
.This version is covered by your current version range and after updating it in your project the build failed.
debug is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
The new version differs by 4 commits.
68b4dc8
4.1.1
7571608
remove .coveralls.yaml
57ef085
copy custom logger to namespace extension (fixes #646)
d0e498f
test: only run coveralls on travis
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.