profile
viewpoint
fansekey xiangshouding Harbin Institute of Technology, nsfocus, baidu Beijing, China www.orrafy.com I'm

miwoow/StudyAndTrain 3

In order to keep our skills of programing. Create this project to train and study programing skills.

fouber/ci-test 2

test travis ci

fouber/fis-parser-utc 2

A parser for fis to compile underscore template.

xiangshouding/Custom-NSView 2

Custom NSView

xiangshouding/cotl 1

Contents of the landscaping

push eventzhangyuanwei/node-images

xiangshouding

commit sha 20aef88a4ead886b926d9c8b503e408547ab5753

[RELEASE] images@3.2.3

view details

push time in 6 days

startedblackberry/Cascades-Samples

started time in 18 days

issue commentzhangyuanwei/node-images

linux 下node版本12.14.0不支持,windows支持

npm install zhangyuanwei/node-images

再试试,现在应该 ok 了;

smallbad

comment created time in 19 days

push eventzhangyuanwei/node-images

xiangshouding

commit sha 5325329c584dbb148a5457a62cfcb9b156a07951

[UPDATE] fix GLIBC version

view details

push time in 19 days

issue commentzhangyuanwei/node-images

linux 下node版本12.14.0不支持,windows支持

用的是 centos 7 么?

ThenMorning notifications@github.com 于2020年7月10日周五 上午11:51写道:

Linux version 3.10.0-862.mt20190308.130.el7.x86_64 (root@gh-hulk-k8s-ep01) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-11) (GCC) ) #1 https://github.com/zhangyuanwei/node-images/issues/1 SMP Fri Mar 8 06:37:16 UTC 2019 glibc-2.17-260.el7_6.5.x86_64 glibc-common-2.17-260.el7_6.5.x86_64 glibc-devel-2.17-260.el7_6.5.x86_64 glibc-headers-2.17-260.el7_6.5.x86_64 我这里同样不行 error: /lib64/libm.so.6: version `GLIBC_2.27' not found

升级了 glibc 2.27 可以了

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/zhangyuanwei/node-images/issues/211#issuecomment-656467160, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAE2DG5Z4PDCQWYB5XMA5F3R22F5HANCNFSM4OKJRBPQ .

smallbad

comment created time in 25 days

issue commentzhangyuanwei/node-images

linux 下node版本12.14.0不支持,windows支持

Linux环境比较咋,你提供一下你的Linux用的啥以及内核、glibc 版本

zhangxiaojian notifications@github.com 于 2020年6月28日周日 上午10:08写道:

linux 下node版本12.14.0不支持,windows支持

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/zhangyuanwei/node-images/issues/211, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAE2DGZFUNJWFVNQQI4OG6DRY2Q3HANCNFSM4OKJRBPQ .

smallbad

comment created time in a month

issue commentfex-team/fis3

fis3

14 没适配

songxk notifications@github.com 于 2020年6月29日周一 下午2:27写道:

  • 操作系统: Arch Linux
  • Node版本: 14.0.4
  • FIS版本: fis3
  • 解决方案:
  • 依赖插件:

fis3 release -wd

[INFO] Currently running fis3 (/usr/lib/node_modules/fis3/)

internal/fs/utils.js:657 throw new ERR_INVALID_ARG_TYPE( ^

TypeError [ERR_INVALID_ARG_TYPE]: The "data" argument must be of type string or an instance of Buffer, TypedArray, or DataView. Received undefined at Object.writeFileSync (fs.js:1380:5) at Function._.write (/usr/lib/node_modules/fis3/lib/util.js:733:8) at F.save (/usr/lib/node_modules/fis3/lib/cache.js:45:14) at /usr/lib/node_modules/fis3/node_modules/fis3-command-release/index.js:62:15 at wrapped (/usr/lib/node_modules/fis3/node_modules/fis3-command-release/lib/chains.js:30:58) at Object.run (/usr/lib/node_modules/fis3/node_modules/fis3-command-release/lib/chains.js:39:9) at Object.exports.run (/usr/lib/node_modules/fis3/node_modules/fis3-command-release/index.js:114:7) at Object.cli.run (/usr/lib/node_modules/fis3/lib/cli.js:259:11) at Liftoff. (/usr/lib/node_modules/fis3/bin/fis.js:36:11) at Liftoff. (/usr/lib/node_modules/fis3/node_modules/liftoff/index.js:197:12) { code: 'ERR_INVALID_ARG_TYPE' }

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/fex-team/fis3/issues/1310, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAE2DG6LKFIVY7NAWQR6L5LRZAX5NANCNFSM4OK6KQIA .

songxk

comment created time in a month

startedWSTxda/MIUI-12-Font-Module

started time in a month

startedemacs-tw/awesome-emacs

started time in 2 months

startedcopy/v86

started time in 2 months

startedOpenEmu/OpenEmu

started time in 2 months

startedProvenance-Emu/Provenance

started time in 2 months

push eventxiangshouding/node-pngcrush

fansekey

commit sha 4a310f917668d357813920c1ed117dd5fe5bea4f

[UPDATE] windows' binding.node

view details

push time in 2 months

issue closedxiangshouding/node-pngcrush

什么时候支持windows平台上的node 10.x吗

从commit消息来看是在支援windows平台的node 10.x版本,预计什么时候会发布吗?

closed time in 2 months

050934

issue closedxiangshouding/node-pngcrush

Newest release version not published to GitHub

The latest release version, 1.0.2, is published to the public npm feed (here). However, that same version doesn't seem to be published as a release in GitHub. Is the missing GitHub release intentional?

The missing release can manifest during an npm install. If, for whatever reason, the install command attempts to hit GitHub to download the necessary .node file, it doesn't find the file and throws a 404:

...
> node-pngcrush@1.0.2 install Z:\a\agent\15\s\node_modules\node-pngcrush
> node ./scripts/install.js

Downloading binary from https://github.com/xiangshouding/node-pngcrush/releases/download/v1.0.2/win32-x64-48_binding.node
##[error]Cannot download "https://github.com/xiangshouding/node-pngcrush/releases/download/v1.0.2/win32-x64-48_binding.node": 
HTTP error 404 Not Found
Hint: If github.com is not accessible in your location
      try setting a proxy via HTTP_PROXY, e.g. 
      export HTTP_PROXY=http://example.com:1234
or configure npm proxy via
      npm config set proxy http://example.com:8080

...

Is this an oversight, or do I need to, say, use npm-shrinkwrap to pin version 1.0.1?

Note: I've created a similar issue for the node-pngquant-native package here.

closed time in 2 months

nsturdivant

issue closedxiangshouding/node-pngcrush

最新代码与 npm 不一致

目前 github 上的最新代码,与 npm 包的不一致 麻烦发下新的 npm 包吧~

closed time in 2 months

iUUCoder

issue closedxiangshouding/node-pngcrush

安装时,提示出下载出错,求解决

www2015:app.nodejs-react2 dreamxyp$ node -v v12.8.1 www2015:app.nodejs-react2 dreamxyp$ npm -v 6.10.2 www2015:app.nodejs-react2 dreamxyp$ www2015:app.nodejs-react2 dreamxyp$ npm install -g node-pngcrush

node-pngcrush@1.0.1 install /Users/dreamxyp/.node_global/lib/node_modules/node-pngcrush node ./scripts/install.js

Downloading binary from https://github.com/xiangshouding/node-pngcrush/releases/download/v1.0.1/darwin-x64-72_binding.node Cannot download "https://github.com/xiangshouding/node-pngcrush/releases/download/v1.0.1/darwin-x64-72_binding.node":

HTTP error 404 Not Found

Hint: If github.com is not accessible in your location try setting a proxy via HTTP_PROXY, e.g.

  export HTTP_PROXY=http://example.com:1234

or configure npm proxy via

  npm config set proxy http://example.com:8080
  • node-pngcrush@1.0.1 updated 2 packages in 7.017s

closed time in 2 months

dreamxyp

issue closedxiangshouding/node-pngcrush

node-pngcrush does not support your node v12.6.0

node-pngcrush does not support your node v12.6.0

closed time in 2 months

callren

push eventxiangshouding/node-pngcrush

xiangshouding

commit sha 549db2b8fb54c6fff2b658863d9ce2cb70889410

[RELEASE] 1.0.2

view details

xiangshouding

commit sha 10f380651fb2eb6434f69a547552378ba6fe64bf

[UPDATE] 1.1.0

view details

push time in 2 months

issue closedxiangshouding/node-pngquant-native

Not supporting for node versions lower than 10

the issue particularly observed when using node 8.x _handle.Pngquant is not a constructor

closed time in 2 months

nikugogoi

issue closedxiangshouding/node-pngquant-native

Newest release versions not published to GitHub

The latest release version, 2.1.3, is published to the public npm feed (here). However, that same version doesn't seem to be published as a release in GitHub. The same seems to be true for 2.1.2. Is there a reason for this? Are the missing GitHub releases intentional?

The missing releases can manifest during an npm install. If, for whatever reason, the install command attempts to hit GitHub to download the necessary .node file, it doesn't find the file and throws a 404:

...
> node-pngquant-native@2.1.3 install Z:\a\agent\15\s\node_modules\node-pngquant-native
> node ./scripts/install.js

Downloading binary from https://github.com/xiangshouding/node-pngquant-native/releases/download/v2.1.3/win32-x64-48_binding.node
##[error]Cannot download "https://github.com/xiangshouding/node-pngquant-native/releases/download/v2.1.3/win32-x64-48_binding.node": 
HTTP error 404 Not Found
Hint: If github.com is not accessible in your location
      try setting a proxy via HTTP_PROXY, e.g. 
      export HTTP_PROXY=http://example.com:1234
or configure npm proxy via
      npm config set proxy http://example.com:8080
...

Is this an oversight, or do I need to, say, use npm-shrinkwrap to pin version 2.1.1?

Note: I've created a similar issue for the node-pngcrush package here.

closed time in 2 months

nsturdivant

issue closedxiangshouding/node-pngquant-native

node-pngquant-native does not support your node v12.8.1

Output this warning while use fis3:

[WARNI] node-pngquant-native does not support your node v12.8.1, report it to https://github.com/xiangshouding/node-pngquant-native/issues

closed time in 2 months

Xiphap

issue closedxiangshouding/node-pngquant-native

does not support your node v9.4.0

node-pngquant-native does not support your node v9.4.0, report it to https://github.com/xiangshouding/node-pngquant-native/issues

mac系统 是否不支持9.4.0版本的node

closed time in 2 months

liuyankai1990

issue closedxiangshouding/node-pngquant-native

HTTP error 404 Not Found

Cannot download "https://github.com/xiangshouding/node-pngquant-native/releases/download/v2.0.1/linux-x64-59_binding.node"

node 9.7.1 npm 5.6.0 ubuntu 17.10

closed time in 2 months

timotejroiko

issue closedxiangshouding/node-pngquant-native

node v.8.9.4 not support

[WARNI] node-pngquant-native does not support your node v8.9.4, report it to ht ps://github.com/xiangshouding/node-pngquant-native/issues

closed time in 2 months

jackrouse

push eventxiangshouding/node-pngquant-native

xiangshouding

commit sha c5e68f8e4faef1934d5252b963b4e8af31fc2511

[RELEASE] 2.2.0

view details

push time in 2 months

push eventxiangshouding/node-pngquant-native

xiangshouding

commit sha 601fd57c0e230eac484c61e80a47e4d240291348

[UPDATE] support >= 10.x node

view details

push time in 2 months

issue closedzhangyuanwei/node-images

请问怎么获取指定坐标的像素值呢?

哈喽, 我有一系列问题, 文档中都未提到:

  1. 有没有获取指定坐标的像素值的函数, 提供从 Image -> (Point -> Pixel) 的映射?
  2. 有没有类似map的接口, 提供从 Pixel -> Pixel 的函数到 Image -> Image 的函数的映射?

closed time in 2 months

luochen1990

issue commentzhangyuanwei/node-images

加载图像报错

#209

jiang842493698

comment created time in 2 months

issue closedzhangyuanwei/node-images

加载图像报错

加载一张jpg的图片报错,报错内容是Error: ..\src\Image.cc:341 Unknow format,有什么方式区分此图片的格式,是否可以加载

closed time in 2 months

jiang842493698

issue closedzhangyuanwei/node-images

Could not use in docker

node-images could not use in official docker image. Guess the reason is official node docker image use musl libc instead of glibc. Is there a plan to support that?

closed time in 2 months

qdechochen

issue commentzhangyuanwei/node-images

Could not use in docker

#173

qdechochen

comment created time in 2 months

issue closedzhangyuanwei/node-images

Windows 64-bit with Unsupported runtime (59)

imagesdoes not yet support your current environment: Windows 64-bit with Unsupported runtime (59)

closed time in 2 months

yanqiangsjz

issue commentzhangyuanwei/node-images

对应linux版本的node10 LTS

#209

alexsunnysun

comment created time in 2 months

issue closedzhangyuanwei/node-images

对应linux版本的node10 LTS

老板,什么时候能更新到linux下node10呀。

closed time in 2 months

alexsunnysun

issue closedzhangyuanwei/node-images

centos7上面用不了

Error: /usr/lib64/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by /www/newwww/nodeServer/node_modules/images/vendor/linux-x64-64/binding.node)

closed time in 2 months

newpanjing

issue closedzhangyuanwei/node-images

windows 7 error

ELECTRON_ASAR.js:166 Uncaught Error: The system cannot find message text for message number 0x%1 in the message file for %2. \?\D:\electron-quick-start\node_modules\images\vendor\win32-x64-64\binding.node at process.module.(anonymous function) [as dlopen] (ELECTRON_ASAR.js:166:20) at Object.Module._extensions..node (internal/modules/cjs/loader.js:740) at Object.module.(anonymous function) [as .node] (ELECTRON_ASAR.js:166:20) at Module.load (internal/modules/cjs/loader.js:620) at tryModuleLoad (internal/modules/cjs/loader.js:559) at Function.Module._load (internal/modules/cjs/loader.js:551) at Module.require (internal/modules/cjs/loader.js:658) at require (internal/modules/cjs/helpers.js:20) at module.exports (D:\electron-quick-start\node_modules\images\scripts\util\binding.js:24) at Object.<anonymous> (D:\electron-quick-start\node_modules\images\index.js:32) module.(anonymous function) @ ELECTRON_ASAR.js:166 Module._extensions..node @ internal/modules/cjs/loader.js:740 module.(anonymous function) @ ELECTRON_ASAR.js:166 Module.load @ internal/modules/cjs/loader.js:620 tryModuleLoad @ internal/modules/cjs/loader.js:559 Module._load @ internal/modules/cjs/loader.js:551 Module.require @ internal/modules/cjs/loader.js:658 require @ internal/modules/cjs/helpers.js:20 module.exports @ D:\electron-quick-start\node_modules\images\scripts\util\binding.js:24 (anonymous) @ D:\electron-quick-start\node_modules\images\index.js:32 (anonymous) @ D:\electron-quick-start\node_modules\images\index.js:247 Module._compile @ internal/modules/cjs/loader.js:711 Module._extensions..js @ internal/modules/cjs/loader.js:722 Module.load @ internal/modules/cjs/loader.js:620 tryModuleLoad @ internal/modules/cjs/loader.js:559 Module._load @ internal/modules/cjs/loader.js:551 Module.require @ internal/modules/cjs/loader.js:658 require @ internal/modules/cjs/helpers.js:20 (anonymous) @ D:\electron-quick-start\js\renderer.js:13 (anonymous) @ D:\electron-quick-start\js\renderer.js:561 Module._compile @ internal/modules/cjs/loader.js:711 Module._extensions..js @ internal/modules/cjs/loader.js:722 Module.load @ internal/modules/cjs/loader.js:620 tryModuleLoad @ internal/modules/cjs/loader.js:559 Module._load @ internal/modules/cjs/loader.js:551 Module.require @ internal/modules/cjs/loader.js:658 require @ internal/modules/cjs/helpers.js:20 (anonymous) @ index.html:75

closed time in 2 months

chaims

issue commentzhangyuanwei/node-images

windows 7 error

#209

chaims

comment created time in 2 months

issue closedzhangyuanwei/node-images

centos 7.4 安装失败

load module error: Error: node_modules/images/vendor/linux-x64-64/binding.node: ELF load command past end of file

closed time in 2 months

yuenshui

issue commentzhangyuanwei/node-images

centos 7.4 安装失败

#209

yuenshui

comment created time in 2 months

issue closedzhangyuanwei/node-images

Missing linux-x64-67_binding.node

missing, somehow meteor.com uses them in a docker container. Can you please add them

closed time in 2 months

nanu-c

issue commentzhangyuanwei/node-images

Missing linux-x64-67_binding.node

#209

nanu-c

comment created time in 2 months

issue closedzhangyuanwei/node-images

Missing bindings for Linux 64-bit with Node.js 8.x

When running in AWS lamba (deployed with serverless), I get the following error:

images could not find a binding for your current environment: Linux 64-bit with Node.js 8.x

Found bindings for the following environments:
- OS X 64-bit with Unsupported runtime (59)

Any chance these bindings could be added?

Thank you in advance!

closed time in 2 months

aybmab

issue commentzhangyuanwei/node-images

Missing bindings for Linux 64-bit with Node.js 8.x

#209 fixed

aybmab

comment created time in 2 months

issue closedzhangyuanwei/node-images

Debian 9.8, NodeJS 10.15.3环境下,可以安装images 3.0.2,但使用时出现`GLIBC_2.27' not found

出错信息详细:

[03-28 09:58:10.566] [ERROR] (node:3206) UnhandledPromiseRejectionWarning: Error: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.27' not found (required by /mnt/slowdb/capps/pai-group-test/pai-devops/node_modules/images/vendor/linux-x64-64/binding.node)

请问这种情况该如何解决,谢谢

closed time in 2 months

wildtang

issue closedzhangyuanwei/node-images

AWS Lambda Node10.x issue

Just wanted to see if you're looking to fix the Node10.x binding so it works on AWS Lambda? AWS are deprecating 8.10 and your Node10.x bindings do not work on Amazon Linux.

At the moment there's a GLIBC incompatibility:

Error: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by /home/ec2-user/test/node_modules/images/vendor/linux-x64-64/binding.node)

Versions on Lambda:

[ec2-user@amzn2 linux-x64-64]$ yum info glibc | grep Version
Version     : 2.26
Version     : 2.26

Also if you could provide instructions for how you call node-gyp as I'm getting segmentation faults no matter how I compile with 10.x

closed time in 2 months

dcarrion87

issue commentzhangyuanwei/node-images

AWS Lambda Node10.x issue

#209 fixed

dcarrion87

comment created time in 2 months

issue commentzhangyuanwei/node-images

npm 安装报错404 node版本7.2.0

#209

846836199

comment created time in 2 months

issue closedzhangyuanwei/node-images

ubuntu 18.04 node 10+ 安装完成,但是运行错

Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic

Node.js v10.15.3

error : 'Segmentation fault (core dumped)'

closed time in 2 months

dodobaba

issue closedzhangyuanwei/node-images

在node12环境下报错

[Node] Error: imagesdoes not yet support your current environment: OS X 64-bit with Unsupported runtime (72) [Node] For more information on which environments are supported please see:

closed time in 2 months

Baiang

issue commentzhangyuanwei/node-images

在node12环境下报错

latest version fixed this bug

Baiang

comment created time in 2 months

issue closedzhangyuanwei/node-images

升级计划(2019.9.18)

现在项目有几个痛点

  • 对于特定 node 版本,由于 v8 版本的更新会导致构建的插件不兼容,所以每次都是按照 node v8 的版本来构建插件版本,node 版本发生跨度比较大的变化,就会导致在新版本上不可用
  • 现在的版本不支持安装时自动构建,之所以这样的原因是许多前端同学的环境没有编译环境,所以一般前面都会提供好编译包。但很可惜的点是,编译包逐步递增导致不得不安装时下载。不然包大小无法控制。如果你的网络环境不太行的话就会导致无法下载成功而安装失败
  • 由于版本迭代,一些功能被迭代没了,这主要是测试用例没有写全

针对以上的几个问题,本次版本进行如下改造

  • 全部使用 n_api 进行编写,把兼容问题交给 Node 自己解决,对于早期的 node 版本逐步不予维护
  • 提供完成的测试用例,保持后续的迭代质量
  • 安装时尝试编译,如果在已经编译好的插件下载失败时。

预计完成时间 10.1 日前

closed time in 2 months

xiangshouding

issue commentzhangyuanwei/node-images

升级计划(2019.9.18)

#209

xiangshouding

comment created time in 2 months

issue closedzhangyuanwei/node-images

这个是同步的还是异步的?

谢谢。

closed time in 2 months

jane00

issue commentzhangyuanwei/node-images

这个是同步的还是异步的?

同步

jane00

comment created time in 2 months

issue closedzhangyuanwei/node-images

cnpm install images 的时候提示下载不了这个 win32-x64-72_binding.node这个文件。怎么办?

Downloading binary from https://github.com/zhangyuanwei/node-images/releases/download/v3.0.2/win32-x64-72_binding.node Cannot download "https://github.com/zhangyuanwei/node-images/releases/download/v3.0.2/win32-x64-72_binding.node":

HTTP error 404 Not Found

closed time in 2 months

momobeizi

issue closedzhangyuanwei/node-images

add electron 8.0 support

images does not yet support your current environment: OS X 64-bit with Unsupported runtime (76)

mac osx: 10.14.6 node: 10.15.3

closed time in 2 months

darknblack

issue commentzhangyuanwei/node-images

add electron 8.0 support

#209

darknblack

comment created time in 2 months

issue closedzhangyuanwei/node-images

window 下运行出错

windows 10 专业版 X64. nodejs 10.15.1

(node:25788) UnhandledPromiseRejectionWarning: Error [50000]: c:\users\xiang\dev\node-images\src\image.cc:581 Unknow format at WrappedImage.loadFromBuffer (D:\game\singleGame\autoBuild\node_modules\images\index.js:54:22) at WrappedImage.loadFromBuffer (D:\game\singleGame\autoBuild\node_modules\images\index.js:147:34) at Function.images.loadFromBuffer (D:\game\singleGame\autoBuild\node_modules\images\index.js:219:27) at Function.images.loadFromFile (D:\game\singleGame\autoBuild\node_modules\images\index.js:211:19) at images (D:\game\singleGame\autoBuild\node_modules\images\index.js:177:24) at main (D:\game\singleGame\autoBuild\runBuild.js:24:17) at process._tickCallback (internal/process/next_tick.js:68:7) at Function.Module.runMain (internal/modules/cjs/loader.js:745:11) at startup (internal/bootstrap/node.js:283:19) at bootstrapNodeJSCore (internal/bootstrap/node.js:743:3)

closed time in 2 months

zhifuliu

issue commentzhangyuanwei/node-images

window 下运行出错

#209

zhifuliu

comment created time in 2 months

issue closedzhangyuanwei/node-images

现在linux环境下node版本10还是应用失败的

现在linux环境下node版本10还是应用失败的,我看您之前有说更新,想请教一下如何才能在10上应用呢

closed time in 2 months

smallbad

issue commentzhangyuanwei/node-images

Linux Node 10 啥时候支持

#209

droidxiao

comment created time in 2 months

issue closedzhangyuanwei/node-images

Linux Node 10 啥时候支持

如题

closed time in 2 months

droidxiao

issue closedzhangyuanwei/node-images

关于支持node12 的版本大概什么时候会出?

您好,请问大概什么时候会出支持node12 的版本呢?

closed time in 2 months

kang888888

issue commentzhangyuanwei/node-images

关于支持node12 的版本大概什么时候会出?

64 位系统已支持,32 暂时没有计划;

kang888888

comment created time in 2 months

push eventzhangyuanwei/node-images

xiangshouding

commit sha 5d6d7befce2695f324ea3bbb1b9a34a0a448a811

[FIX] fix little issue

view details

push time in 2 months

push eventzhangyuanwei/node-images

xiangshouding

commit sha eb7db16641d4083f4469653dec38d0f321d1aa40

[FIX] fix a little problem

view details

push time in 2 months

push eventzhangyuanwei/node-images

xiangshouding

commit sha d64b00394a39869e60334aa2f87711052e56a8d2

[RELEASE] 3.2.0

view details

push time in 2 months

push eventzhangyuanwei/node-images

xiangshouding

commit sha 111ed4e2b5801bd2355156ca4f8f7ba4c7ddac53

[FIX] support diff arch

view details

push time in 2 months

issue commentzhangyuanwei/node-images

关于支持node12 的版本大概什么时候会出?

大概更新了一下代码,解决了一些问题,等我近期发布新版;

kang888888

comment created time in 2 months

push eventzhangyuanwei/node-images

fansekey

commit sha ebe4a0a65cebb98bd4423eed5613d02db868ff67

[FIX] windows build error

view details

fansekey

commit sha 16f4467f835dfbf5b9f2cce80fbf7fa60144bdf2

[FIX] windows build error

view details

fansekey

commit sha ccb1aa1490daa5863978f923277fd69eff3eae14

[FIX] windows build error

view details

push time in 2 months

push eventxiangshouding/gyp

fansekey

commit sha b764bb637c26b61527b3eec63f7eb450d16bf472

[FIX] windows build error

view details

push time in 2 months

push eventxiangshouding/gyp

fansekey

commit sha 8abf59df477a518ab16cf3e3c7dd0d7dac3844fd

[FIX] windows build error

view details

push time in 2 months

issue commentxiangshouding/node-pngcrush

Newest release version not published to GitHub

what is your node version?

Nick Sturdivant notifications@github.com 于 2020年5月26日周二 上午12:16写道:

The latest release version, 1.0.2, is published to the public npm feed ( here https://www.npmjs.com/package/node-pngcrush/v/1.0.2). However, that same version doesn't seem to be published as a release in GitHub. Is the missing GitHub release intentional?

The missing release can manifest during an npm install. If, for whatever reason, the install command attempts to hit GitHub to download the necessary .node file, it doesn't find the file and throws a 404:

...

node-pngcrush@1.0.2 install Z:\a\agent\15\s\node_modules\node-pngcrush node ./scripts/install.js

Downloading binary from https://github.com/xiangshouding/node-pngcrush/releases/download/v1.0.2/win32-x64-48_binding.node ##[error]Cannot download "https://github.com/xiangshouding/node-pngcrush/releases/download/v1.0.2/win32-x64-48_binding.node": HTTP error 404 Not Found Hint: If github.com is not accessible in your location try setting a proxy via HTTP_PROXY, e.g. export HTTP_PROXY=http://example.com:1234 or configure npm proxy via npm config set proxy http://example.com:8080

...

Is this an oversight, or do I need to, say, use npm-shrinkwrap to pin version 1.0.1?

Note: I've created a similar issue for the node-pngquant-native package here https://github.com/xiangshouding/node-pngquant-native/issues/32.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/xiangshouding/node-pngcrush/issues/62, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAE2DG6Z2LQZHFAZHQIKNEDRTKKXLANCNFSM4NJUN3BQ .

nsturdivant

comment created time in 2 months

issue commentzhangyuanwei/node-images

关于支持node12 的版本大概什么时候会出?

reallocarray 看一下是不是被注释了;

kang888888 notifications@github.com 于2020年5月28日周四 下午2:03写道:

我后面看网上说是缺了头文件,补了一个,内容如下: /** This file is part of the Mingw32 package.

  • unistd.h maps (roughly) to io.h

/ #ifndef _UNISTD_H #define _UNISTD_H #include <io.h> #include <process.h> #endif / _UNISTD_H */

但还是会报错: C:\test\node-images>node-gyp build gyp info it worked if it ends with ok gyp info using node-gyp@5.1.1 gyp info using node@12.16.3 | win32 | x64 gyp info spawn C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\15.0\Bin\MSBuild.exe gyp info spawn args [ gyp info spawn args 'build/binding.sln', gyp info spawn args '/clp:Verbosity=minimal', gyp info spawn args '/nologo', gyp info spawn args '/p:Configuration=Release;Platform=x64' gyp info spawn args ] 在此解决方案中一次生成一个项目。若要启用并行生成,请添加“/m”开关。 libpng.vcxproj -> C:\test\node-images\build\Release\libpng.lib libjpeg-turbo.vcxproj -> C:\test\node-images\build\Release\libjpeg-turbo.lib dgif_lib.c gif_err.c c:\test\node-images\gyp\third-party\giflib\lib\dgif_lib.c(383): warning C4018: “<”: 有符号/无符号不匹配 [C:\test\node-images\build\gyp\gyp\gif lib.vcxproj] giflib.vcxproj -> C:\test\node-images\build\Release\giflib.lib zlib.vcxproj -> C:\test\node-images\build\Release\zlib.lib 正在创建库 C:\test\node-images\build\Release\binding.lib 和对象 C:\test\node-images\build\Release\binding.exp giflib.lib(dgif_lib.obj) : error LNK2001: 无法解析的外部符号 reallocarray [C:\test\node-images\build\binding.vcxproj] C:\test\node-images\build\Release\binding.node : fatal error LNK1120: 1 个无法解析的外部命令 [C:\test\node-images\build\binding.vcxproj] gyp ERR! build error gyp ERR! stack Error: C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\15.0\Bin\MSBuild.exe failed with exit code: 1 gyp ERR! stack at ChildProcess.onExit (C:\node\node-v12.16.3-win-x64\node_modules\node-gyp\lib\build.js:194:23) gyp ERR! stack at ChildProcess.emit (events.js:310:20) gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12) gyp ERR! System Windows_NT 10.0.18362 gyp ERR! command "C:\node\node-v12.16.3-win-x64\node.exe" "C:\node\node-v12.16.3-win-x64\node_modules\node-gyp\bin\node-gyp.js" "build" gyp ERR! cwd C:\test\node-images gyp ERR! node -v v12.16.3 gyp ERR! node-gyp -v v5.1.1 gyp ERR! not ok

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/zhangyuanwei/node-images/issues/209#issuecomment-635124471, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAE2DG4V2N7PHR5FJBTV7X3RTX5EBANCNFSM4NMADMHA .

kang888888

comment created time in 2 months

issue commentzhangyuanwei/node-images

关于支持node12 的版本大概什么时候会出?

代码都是现成的,可以尝试自己编译。

kang888888 notifications@github.com 于 2020年5月27日周三 下午6:32写道:

您好,请问大概什么时候会出支持node12 的版本呢?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/zhangyuanwei/node-images/issues/209, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAE2DG7LA2JBTC6I64LJFHTRTTT45ANCNFSM4NMADMHA .

kang888888

comment created time in 2 months

issue commentxiangshouding/node-pngquant-native

Node.js v10 tag and publish please.

DONE You can retry, thx!

Jeremie Perdereau notifications@github.com 于2020年4月23日周四 下午6:18写道:

Hello,

If you can tag and publish your latest commit ed734be https://github.com/xiangshouding/node-pngquant-native/commit/ed734be62b4d68306d29bf8de470046fb9832f83 that will wonderful.

Thx in advance.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/xiangshouding/node-pngquant-native/issues/31, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAE2DG562WHOGKKMDE63IRTROAIZDANCNFSM4MO55SZA .

jperdereau

comment created time in 3 months

push eventxiangshouding/node-pngquant-native

xiangshouding

commit sha b5847cdd5de0151d7dec0465e2d87363befa0e2d

[RELEASE] VERSION 2.1.3

view details

push time in 3 months

push eventzhangyuanwei/node-images

fansekey

commit sha af868980c9b3642e2af9952fc2b17abd9eccd2a9

[UPDATE] linux version support

view details

push time in 3 months

push eventxiangshouding/node-pngquant-native

xiangshouding

commit sha 9a7e2a14b440b7ebf1bed54af350c3cc54554930

[UPDATE] npm ignore gyp

view details

push time in 3 months

more