Incorrect paths for @blueprintjs source maps that produce multiple warnings on project compilation

Environment

• Package version(s): @blueprintjs/core@3.15.1
• Browser and OS versions: Chrome 73.0.3683.86, OS X 10.14.4

If possible, link to a minimal repro: https://github.com/newtriks/bp_example

Steps to reproduce

1. npm install --save @blueprintjs/core @blueprintjs/datetime
2. cd node_modules/@blueprintjs/datetime/lib/css/
3. Check path in blueprint-datetime.css.map for _variables.scss
4. Using path list dir for _variables.scss e.g. ls ../../../../node_modules/@blueprintjs/core/src/common/

Actual behavior

Output: ls: ../../../../node_modules/@blueprintjs/core/src/common/: No such file or directory

This was discovered by all the warnings on compilation of the project:

Expected behavior

Outputs files in the common directory e.g. the source map points to the correct file

Possible solution

Step up another directory e.g. ls ../../../../../node_modules/@blueprintjs/core/src/common/

Output:

_color-aliases.scss             alignment.ts                    intent.ts
_colors.scss                    boundary.ts                     interactionMode.ts
_flex.scss                      classes.ts                      keys.ts
_mixins.scss                    colors.ts                       position.ts
_react-transition.scss          constructor.ts                  props.ts
_variables.scss                 elevation.ts                    utils
abstractComponent.ts            errors.ts                       utils.ts
abstractPureComponent.ts        index.ts

Seems the same as this closed issue: https://github.com/palantir/blueprint/issues/2728

[0xhjohnson]

Experiencing same issue using parcel@1.12.4

[MaximeBernard]

I just encountered the same issue using Parcel.

Any update on this? Any workaround?