#4001 🐛 bug report

Applying @parcel/transformer-raw to a file causes it to be renamed as if it was an asset rather than an entry.

🎛 Configuration (.babelrc, package.json, cli command)

// .parcelrc
{
	"extends": ["@parcel/config-default"],
	"transforms": {
		"*.json": ["@parcel/transformer-raw"],
	}
}

// entry.json
{}

$ parcel build entry.json

parseISO v2 documentation currently states

The previous parse implementation was renamed to parseISO.

parse v2 documentation currently states

Old parse was renamed to toDate. Now parse is a new function which parses a string using a provided format.

I think considering the sentence is to divert people who have previously been using v1 parse to the correct v2 equivalent, it only

Hi, I've been trying to figure out from the docs (and google) to implement externalization of modules in Browserify with no luck. I've implemented transform-runtime plugins, and used .external(filename) in Gulp and tried to use require() in another module ... but I general cannot figure out from the docs what part or parts I'm missing in making this work.

Could someone please, add a brief secti

Description

Bit does not generate docs for React TS components.

for example:

https://bit.dev/eden/react-ts-demo

Specifications

• Bit version: 14.7.4
• Node version: 10.15.3
• npm / yarn version: 6.4.1 / 1.16.0
• Platform: macOS
• Bit compiler (include version): bit.envs/compilers/react-typescript@3.1.44
• Bit tester (include version):

Context and additional inf

I have a project that is in a monorepo and uses yarn right now.

I'm considering migrating to pnpm for the monorepo, as well as all other projects I contribute to, as I have a small SSD as local storage (and with Windows...). However, it would be ideal if there was compatibility between yarn's workspaces and pnpm, so that we don't have to jump "all in" to it.

To this end, yarn allows packages

Create unit test that assert that these types of queries will work in a Liquid template.

The npm pages all say something like "Unable to find a readme for redux-dynamic-modules@5.2.0", which looks a bit concerning when browsing potential packages:
https://www.npmjs.com/package/redux-dynamic-modules

I think there should at least be a minimal readme per package included, which gives a short overview and points to the github page and/or homepage for more details.

I really think th

In the README, maybe very briefly explain how to use a fork you created in GitHub, how to push a change back to that fork on GitHub, and then mention you can use that to open a PR on the original project?

For example, if you fork rsc.io/quote in the GitHub web interface to github.com/thepudds/quote, then use gohack + git to use that fork:

cd $(mktemp -d)                         # cr

After encountering dependency-check-team/dependency-check#112 I tried looking into how that project uses detective and the various "extensions", such as detective-typescript that enabled foreign syntax. It was not immediately obvious how this worked, seeing no explicit interfaces where detective was wrapped by or passed some "extension"

Could

https://github.com/Pext/Pext/blob/master/docs/installation.rst contains instructions for openSUSE, but more repositories are available (despite being untested).

These need to be documented for the relevant distributions:
Stable: https://download.opensuse.org/repositories/home:/TheLastProject:/python-pext/
Nightly: https://download.opensuse.org/repositories/home:/TheLastProject:/python-pext:/d