michael-ciniawsky / postcss-load-options Goto Github PK

Version 6.0.12 of postcss just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As postcss 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 💪

Your Greenkeeper Bot 🌴

Version 6.0.14 of postcss was just published.

This version is covered by your current version range and after updating it in your project the build failed.

postcss 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.

Your Greenkeeper Bot 🌴

Version 5.2.6 of postcss just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As postcss 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 💪

Your Greenkeeper Bot 🌴

Version 3.0.4 of jsdoc-to-markdown was just published.

This version is covered by your current version range and after updating it in your project the build failed.

jsdoc-to-markdown 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.

Your Greenkeeper Bot 🌴

Version 5.2.12 of postcss just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As postcss 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 💪

Your Greenkeeper Bot 🌴

Problem

postcss-load-options overwrites the options object it receives
in-place, which causes a crash when the given object is actually memoized.

Details

When postcss-load-options is invoked for processing a second file, node
throws an assertion as require is called with a non-string argument.

That specific problem may already be fixed by #18, but the presence of this
other bug also triggers it even if the user gives a string to be required.

Error Logs

{ AssertionError: path must be a string
    at Module.require (module.js:497:3)
    at require (internal/module.js:20:19)
    at options (.../node_modules/postcss-load-options/lib/options.js:17:22)
    at .../node_modules/postcss-load-config/index.js:68:18
  name: 'AssertionError',
  actual: false,
  expected: true,
  operator: '==',
  message: 'path must be a string',
  generatedMessage: false }

Issue [ Code ]

postcss.config.js:

const memoize = require('memoizee')
const plugins = require('./postcss.plugins.js')

const config = memoize((production, parser) => {
  return Object.assign({
    plugins: plugins(production, parser)
  }, parser != null ? { parser } : {})
}, { primitive: true, length: false })

// const sugarss = require('sugarss')

module.exports = function postcssConfig (ctx) {
  return config(
    ctx.env === 'production',
    // 'sugarss' until https://github.com/michael-ciniawsky/postcss-load-options/pull/18 is released
    ctx.webpack.resourcePath.endsWith('.sss') ? 'sugarss' : null
  )
}

config, when called, will return the same object for the same arguments, so modifying the object in postcss-load-options contaminates the memoization cache, replacing options.parser with the result of require(options.parser), which breaks the workaround :)

I can work around it by returning a new copy of the object every time, but adding workarounds to make workarounds work is not optimal.

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 11.6.0 of nyc was just published.

This version is covered by your current version range and after updating it in your project the build failed.

nyc 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.

Your Greenkeeper Bot 🌴

Version 6.0.22 of postcss was just published.

This version is covered by your current version range and after updating it in your project the build failed.

postcss 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.

Your Greenkeeper Bot 🌴

Version 6.0.15 of postcss was just published.

This version is covered by your current version range and after updating it in your project the build failed.

postcss 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.

Your Greenkeeper Bot 🌴

Version 3.0.1 of jsdoc-to-markdown was just published.

This version is covered by your current version range and after updating it in your project the build failed.

jsdoc-to-markdown 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.

Your Greenkeeper Bot 🌴

Version 5.2.8 of postcss just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As postcss 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 💪

Your Greenkeeper Bot 🌴

Version 6.0.9 of postcss just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As postcss 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 💪

Your Greenkeeper Bot 🌴

Version 2.2.0 of cosmiconfig just got published.

This version is covered by your current version range and after updating it in your project the build failed.

cosmiconfig 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 💪

Your Greenkeeper Bot 🌴

Version 11.7.1 of nyc was just published.

This version is covered by your current version range and after updating it in your project the build failed.

nyc 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.

Your Greenkeeper Bot 🌴

Version 6.0.6 of postcss just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As postcss 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 💪

Your Greenkeeper Bot 🌴

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 6.0.21 of postcss was just published.

This version is covered by your current version range and after updating it in your project the build failed.

postcss 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.

Your Greenkeeper Bot 🌴

Version 2.11.16 of coveralls just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As coveralls 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 💪

Your Greenkeeper Bot 🌴

Version 2.13.2 of coveralls just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As coveralls 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 💪

Your Greenkeeper Bot 🌴

Version 3.0.3 of jsdoc-to-markdown was just published.

This version is covered by your current version range and after updating it in your project the build failed.

jsdoc-to-markdown 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.

Your Greenkeeper Bot 🌴

Version 11.3.0 of nyc was just published.

This version is covered by your current version range and after updating it in your project the build failed.

nyc 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.

Your Greenkeeper Bot 🌴

Version 11.7.2 of nyc was just published.

This version is covered by your current version range and after updating it in your project the build failed.

nyc 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.

Your Greenkeeper Bot 🌴

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 6.0.20 of postcss was just published.

This version is covered by your current version range and after updating it in your project the build failed.

postcss 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.

Your Greenkeeper Bot 🌴