Emily McLin

Ok, now that you said that... something finally clicked and I get it. When I was reading the info about PWM: https://github.com/jperkin/node-rpio#pwm I didn't make the connection that I had...

@danez I've created an example repo stripped down to the bare functionality, with steps to reproduce: https://github.com/amclin/poc-semantic-release-npm-error ### Steps to Reproduce 1. Use Node 12 or Node 14, with default...

Thanks @danez, I can confirm `--no-audit` is a workaround for the issue in my project, and I'm determining whether that's the best course of action.

@travi I'm already doing that. But the semantic-release plugins aren't included via that method.

#357 may be related Seems mixing NPM 7 as a dependency into stacks that don't explicitly use NPM 7 is problematic.

How would this even work? If you are developing for email, you should be finding other markup structures to solve for the challenge you see. Since pseudo selectors can't be...

`
` is a line return character. Shouldn't cause a problem to have it in there, but if you're concerned, try doing some cleanup on your input HTML to replace Windows...

Ruby 1.9 is still common since it's the default included in OSX (until Mavericks). So I think dropping Hpricot support is premature. Nokogiri isn't supported on 1.9.

Nokogiri (the alternative to Hpricot) requires Ruby 1.9.2 or later. Until this past summer, Apple was shipping Ruby 1.8.7. Hence, dropping Hpricot support would prevent OSX users from using Premailer...

I've done a bunch of digging the past couple of days as Ruby 1.9 and 2.0 has begun forcing the Nokogiri issue in my build systems. I've discovered that Nokogiri...