Skip to content
This repository was archived by the owner on Jul 24, 2024. It is now read-only.
This repository was archived by the owner on Jul 24, 2024. It is now read-only.

The compiled binary should be also cached. #1882

@abcfy2

Description

@abcfy2
  • NPM version (npm -v): 4.1.2
  • Node version (node -v): v6.9.5
  • Node Process (node -p process.versions):
{ http_parser: '2.7.0',
  node: '6.9.5',
  v8: '5.1.281.89',
  uv: '1.9.1',
  zlib: '1.2.8',
  ares: '1.10.1-DEV',
  icu: '56.1',
  modules: '48',
  openssl: '1.0.2k' }
  • Node Platform (node -p process.platform): linux
  • Node architecture (node -p process.arch): x64
  • node-sass version (node -p "require('node-sass').info"):
node-sass	4.5.0	(Wrapper)	[JavaScript]
libsass  	3.5.0.beta.2	(Sass Compiler)	[C/C++]
  • npm node-sass versions (npm ls node-sass):

I find the compiled binary not be cached in ~/.npm/node-sass. So If the node-modules/ dir removed will download or compile again.

tree ~/.npm/node-sass
/home/fengyu/.npm/node-sass
├── 3.13.1
│   ├── linux-x64-48_binding.node
│   ├── package
│   │   └── package.json
│   └── package.tgz
├── 4.2.0
│   ├── package
│   │   └── package.json
│   └── package.tgz
├── 4.3.0
│   ├── linux-x64-48_binding.node
│   ├── package
│   │   └── package.json
│   └── package.tgz
└── 4.5.0
    ├── package
    │   └── package.json
    └── package.tgz

8 directories, 10 files

If the downloading pre-compiled binary failed(4.5.0), and the compiled binary not be cached in ~/.npm/node-sass/. I think it's better to cache the compiled binary as well.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions