You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 9, 2024. It is now read-only.
I use ejson-shell-parser : 1.2.2 together with bson : 5.0.1 (aka the latest versions at the time of writing this issue). When I bundle my application with Webpack, I do get the following warning:
WARNING in ./node_modules/ejson-shell-parser/dist/ejson-shell-parser.esm.js 177:25-33
export 'Map' (imported as 'bson') was not found in 'bson' (possible exports: BSON, BSONError, BSONRegExp, BSONRuntimeError, BSONSymbol, BSONType, BSONValue, BSONVersionError, Binary, Code, DBRef, Decimal128, Double, EJSON, Int32, Long, MaxKey, MinKey, ObjectId, Timestamp, UUID, calculateObjectSize, deserialize, deserializeStream, serialize, serializeWithBufferAndIndex, setInternalBufferSize)
The export of Map from bson has been removed in the release 5.0.0 (see NODE-4712 in the release notes).
esjson-shell-parser is supposed to be compatible with bson 5 since the release 1.2.1 (see this PR). Unfortunately, this change seems to be the one triggering a warning during the Webpack build.
The text was updated successfully, but these errors were encountered:
thomas-jakemeyn
changed the title
Webpack warning: 'Map' was not found in 'bson'.
Webpack warning: 'Map' was not found in 'bson'
Mar 1, 2023
I use
ejson-shell-parser : 1.2.2
together withbson : 5.0.1
(aka the latest versions at the time of writing this issue). When I bundle my application with Webpack, I do get the following warning:The export of
Map
frombson
has been removed in the release 5.0.0 (see NODE-4712 in the release notes).esjson-shell-parser
is supposed to be compatible with bson 5 since the release 1.2.1 (see this PR). Unfortunately, this change seems to be the one triggering a warning during the Webpack build.The text was updated successfully, but these errors were encountered: