Document how to depend on source-map 0.6.X for old nodes and 0.7.0 for new nodes

[devongovett]

We're currently working on source map support in Parcel: parcel-bundler/parcel#506. We'd love to take advantage of the WASM version of source-map in 0.7, but we also need to support Node < 8 users. Is there a way the source-map library could fall back to a JS version for Node < 8 users?

[fitzgen]

Folks, there's a reason that a "+1" button exists: so you don't have to leave a comment containing only "+1".

[fitzgen]

I have no interest maintaining two versions of source map parsing and querying, nor incurring the additional code size bloat.

I suggest using the old version of the library if you have to support old node versions, or alternatively setting up some kind of feature detection scheme.

I'll leave this issue open for adding documentation on how to depend on 0.6.X for old nodes and 0.7.0 for new ones.

[deadalusai]

For users of Yarn
For client code, adding the following snippet to package.json will pin source-map to 0.6.x versions:

"resolutions": {
    "source-map": "~0.6.1"
}

This may be useful while we wait for downstream packages to update for the changes in 0.7.0 (or pin to 0.6.x).

Is there a similar solution for NPM users?

[fimius23]

Why doesn't this project follow semver so that I'm protected from this version?

[tromey]

Why doesn't this project follow semver so that I'm protected from this version?

It does; semver treats major version 0 specially. I think it would probably be a good idea to just admit that this package is heavily used and release 1.0.

[fitzgen]

That sounds good to me

[jkrems]

In the meantime node <8 has become less relevant (I'll claim) and @parcel/source-map has been published. I'll close this issue but leave #331 open which is somewhat related.