Sergey S. Volkov

Results 13 issues of Sergey S. Volkov

some gulp tasks not worked. I added jshint for resolve this problem. If I npm install without jshint ![wheniintsallnpm](https://cloud.githubusercontent.com/assets/16340911/20386431/ae7a0d9a-accc-11e6-8a1d-bede09d5a726.png) And run task 'scripts' ![2016-11-17_1352](https://cloud.githubusercontent.com/assets/16340911/20386553/38371e6a-accd-11e6-8bcf-21dc17bde5f9.png)

Currently utility output a lot of warnings about duplicate method naming. I think it should be fixed when custom operation id generator will be improved.

enhancement
next major release

## Environment Windows 10, Webpack 5, node 14.18.3, ``` "@linaria/babel-preset": "^4.1.2", "@linaria/core": "^4.1.1", "@linaria/react": "^4.1.2", "webpack": "^5.74.0", "webpack-bundle-analyzer": "^4.5.0", "webpack-cli": "^4.10.0", "webpack-closure-compiler": "^2.1.6", "webpack-dev-server": "^4.10.0" "@babel/core": "^7.18.10", "@babel/plugin-syntax-dynamic-import": "^7.8.3", "@babel/polyfill":...

needs: complete repro 🖥️
bundler: webpack 📦
platform: ssr 🛠️
cat: modules aliasing 🔗
bug report 🦗

Improvenments: - command `fb web` will have only one instance of NodeJS application. First call `fb web -p SOME_PORT` create a server hosted on port `SOME_PORT`. But call `fb web`...

Command "npm run build ..." In some project I have scripts in package.json ``` { ... "build": "webpack", ... "test": "npm run build && mocha "test/unit/**/*.js" --compilers js:babel-core/register" } Flamebird...

bug
good first issue
invalid

Symbols like ``, `` are not showed in logs as text and rendered like html elements ![image](https://user-images.githubusercontent.com/16340911/51616656-a13a6100-1f3b-11e9-96f2-8e79ea6e3eba.png)

bug
good first issue
invalid

Approximate representation of how it looks like. - Several active tasks (max 4) ![image](https://user-images.githubusercontent.com/16340911/52838675-8b682800-3104-11e9-96b4-d4060a89b52a.png)

enhancement
web-version

Now css files have state are raw in production build Needs to update webpack config. Definitely update css build configuration for the fixing this problem

good first issue
invalid
web-version

I guess logs should be like `${taskName} | ${logLine1}` `${taskName} | ${logLine2}` etc. For a more good viewing logs For example ``` task1 | webpack start building... task2 | styles...

enhancement
help wanted

Sometimes we have projects with not only one package.json file. And for resolving this problem we should add the ability of parsing several package.json files

enhancement