Closed sukrosono closed 6 years ago
None of the core maintainers use Debian as far as I know. We did have one person report an issue a while back either on Ubuntu or Debian but I'm not sure we ever reached a resolution. I don't think we'll be able to officially support it as most of us can't test on it...
That said, let me try to address the issues you're seeing:
Prism does not support this language: ts
These are known and due to the worker-loader
s README
which we pull in dynamically. I've been meaning to fix that and will submit a PR on that repo shortly.
Bus error.
I've never seen this however I've used v6.x versions for a while with no issues. However, I just recently got nvm
set up so I'll test it out. However, it seems more related to an issue with libsass
on those systems. I'd look at node-sass
for more information on how to fix on your OS.
Tested with v6.11.4 on macOS 10.12.6 and ran into no issues. Closing but if you find an answer, we'd be happy to have you submit a PR to our .github/CONTRIBUTING.md
with a note about Debian/Ubuntu usage.
See webpack-contrib/worker-loader#112 for the fix to the Prism does not support this language: ts
build warnings.
Thanks for your work jack.
either on Ubuntu or Debian but I'm not sure we ever reached a resolution.
So do i-- since i use nvm, I just switch to v7.x.x .
Closing but if you find an answer.....
Basically, it's not an answer but a note.
Note that on debian derivative, use node >= 7.0.0 to avoid unnecessary problem.
Did you find it's worth doing and acceptable?
Yeah I think it's worth doing. I would add it as another blockquote under the two that are already at the bottom of the Setup section:
I would elaborate what you had to something like:
On Debian and Ubuntu operating systems you may have to use a version of node greater than
v7.0.0
to avoid build errors withnode-sass
. However, please note that we don't officially support building on these systems.
Sorry, still questioning.
Why use "of node greater than v7.0.0
" instead of ">= v7.0.0
"?
That way is fine too and yeah I guess it's a bit more clear what the semver range is.
I use debian, and i try install dev dep when using 6.11.4, but it yell
Then i try use v7.10.1 , but it error so i try
npm rebuild node-sass --force
since i found it on error log (without removing node_modules directory). Since it's kinda forever looping, i cancel it and remove node_modules. Then reinstall dev dep on v7.10.1 , till now seems working fine.failure log v6.11.4
``` > webpack.js.org@0.1.2 start /home/project/under_git/webpack.js.org > npm run init:generated && npm run fetch && node ./antwar.bootstrap.js develop > webpack.js.org@0.1.2 init:generated /home/project/under_git/webpack.js.org > mkdirp ./generated/loaders && mkdirp ./generated/plugins > webpack.js.org@0.1.2 fetch /home/project/under_git/webpack.js.org > sh src/scripts/fetch.sh Fetched 37 files: webpack-contrib/json-loader,webpack-contrib/raw-loader,webpack-contrib/coffee-loader,webpack-contrib/css-loader,webpack-contrib/style-loader,webpack-contrib/script-loader,webpack-contrib/less-loader,webpack-contrib/bundle-loader,webpack-contrib/val-loader,webpack-contrib/file-loader,webpack-contrib/url-loader,webpack-contrib/i18n-loader,webpack-contrib/json5-loader,webpack-contrib/worker-loader,webpack-contrib/jshint-loader,webpack-contrib/imports-loader,webpack-contrib/exports-loader,webpack-contrib/mocha-loader,webpack-contrib/coverjs-loader,webpack-contrib/expose-loader,webpack-contrib/node-loader,webpack-contrib/coffee-redux-loader,webpack-contrib/transform-loader,webpack-contrib/html-loader,webpack-contrib/sass-loader,webpack-contrib/source-map-loader,webpack-contrib/react-proxy-loader,webpack-contrib/null-loader,webpack-contrib/multi-loader,webpack-contrib/istanbul-instrumenter-loader,webpack-contrib/yaml-frontmatter-loader,webpack-contrib/svg-inline-loader,webpack-contrib/restyle-loader,webpack-contrib/gzip-loader,webpack-contrib/cache-loader,webpack-contrib/thread-loader,webpack-contrib/polymer-webpack-loader Fetched 1 file: babel/babel-loader Fetched 1 file: postcss/postcss-loader Fetched 1 file: peerigon/extract-loader Fetched 10 files: webpack-contrib/i18n-webpack-plugin,webpack-contrib/component-webpack-plugin,webpack-contrib/compression-webpack-plugin,webpack-contrib/extract-text-webpack-plugin,webpack-contrib/copy-webpack-plugin,webpack-contrib/npm-install-webpack-plugin,webpack-contrib/babel-minify-webpack-plugin,webpack-contrib/uglifyjs-webpack-plugin,webpack-contrib/zopfli-webpack-plugin,webpack-contrib/closure-webpack-plugin Fetched 1 file: support-backers.json Fetched 1 file: starter-kits-data.json Prism does not support this language: ts Prism does not support this language: ts Prism does not support this language: ts (node:10964) DeprecationWarning: loaderUtils.parseQuery() received a non-string value which can be problematic, see https://github.com/webpack/loader-utils/issues/56 parseQuery() will be replaced with getOptions() in the next major version of loader-utils. ERROR in ./node_modules/css-loader!./node_modules/postcss-loader/lib!./node_modules/sass-loader/lib/loader.js?{"includePaths":["src/styles/partials"]}!./src/components/Logo/Logo.scss Module build failed: Error: Missing binding /home/project/under_git/webpack.js.org/node_modules/node-sass/vendor/linux-x64-48/binding.node Node Sass could not find a binding for your current environment: Linux 64-bit with Node.js 6.x Found bindings for the following environments: - Linux 64-bit with Node.js 7.x This usually happens because your environment has changed since running `npm install`. Run `npm rebuild node-sass --force` to build the binding for your current environment. at module.exports (/home/project/under_git/webpack.js.org/node_modules/node-sass/lib/binding.js:15:13) at Object.do you find this is reproducible? if yes, do you want a PR to .github/CONTRIBUTING.md ?