[COMPASS-5724] Find a way to remove special webpack export from plugins Created: 12/Apr/22  Updated: 29/Oct/23  Resolved: 26/Apr/22

Status: Closed
Project: Compass
Component/s: None
Affects Version/s: None
Fix Version/s: No version

Type: Task Priority: Major - P3
Reporter: Sergey Petushkov Assignee: Sergey Petushkov
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to COMPASS-5723 Investigate compass-aggregations / co... Closed
Documentation Changes: Not Needed

 Description   

We use the exports.webpack export path as a way to allow us bundling Compass from source, at the same time it creates some issues for teams that depend on plugins in their applications. We should investigate a way to remove this exports.webpack export from plugins package.json. One option can be using mainFields and exportsFields in our webpack configuration



 Comments   
Comment by Githook User [ 20/Apr/22 ]

Author:

{'name': 'Sergey Petushkov', 'email': 'petushkov.sergey@gmail.com', 'username': 'gribnoysup'}

Message: chore(webpack-config-compass): Replace exports.webpack with custom exports key COMPASS-5724 (#2990)

  • chore(webpack-config-compass): Replace exports.webpack with custom exports key

`exports.webpack` helped us bundle Compass from source, but at the same time
it was messing with external users of published packages, specifically cloud
team was having troubles with it and had to add special aliases in their webpack
configuration to work around the issue

Using custom main and exports keys completely avoids the issue as these will
be ignored by any other webpack configuration unless explicitly specified

  • chore(webpack-config-compass): Reformat
Comment by Githook User [ 19/Apr/22 ]

Author:

{'name': 'Sergey Petushkov', 'email': 'petushkov.sergey@gmail.com', 'username': 'gribnoysup'}

Message: chore(webpack-config-compass): Replace exports.webpack with custom exports key COMPASS-5724 (#2990)

  • chore(webpack-config-compass): Replace exports.webpack with custom exports key

`exports.webpack` helped us bundle Compass from source, but at the same time
it was messing with external users of published packages, specifically cloud
team was having troubles with it and had to add special aliases in their webpack
configuration to work around the issue

Using custom main and exports keys completely avoids the issue as these will
be ignored by any other webpack configuration unless explicitly specified

  • chore(webpack-config-compass): Reformat
Comment by Githook User [ 19/Apr/22 ]

Author:

{'name': 'Sergey Petushkov', 'email': 'petushkov.sergey@gmail.com', 'username': 'gribnoysup'}

Message: chore(webpack-config-compass): Replace exports.webpack with custom exports key COMPASS-5724 (#2990)

  • chore(webpack-config-compass): Replace exports.webpack with custom exports key

`exports.webpack` helped us bundle Compass from source, but at the same time
it was messing with external users of published packages, specifically cloud
team was having troubles with it and had to add special aliases in their webpack
configuration to work around the issue

Using custom main and exports keys completely avoids the issue as these will
be ignored by any other webpack configuration unless explicitly specified

  • chore(webpack-config-compass): Reformat
Comment by Githook User [ 19/Apr/22 ]

Author:

{'name': 'Sergey Petushkov', 'email': 'petushkov.sergey@gmail.com', 'username': 'gribnoysup'}

Message: chore(webpack-config-compass): Replace exports.webpack with custom exports key COMPASS-5724 (#2990)

  • chore(webpack-config-compass): Replace exports.webpack with custom exports key

`exports.webpack` helped us bundle Compass from source, but at the same time
it was messing with external users of published packages, specifically cloud
team was having troubles with it and had to add special aliases in their webpack
configuration to work around the issue

Using custom main and exports keys completely avoids the issue as these will
be ignored by any other webpack configuration unless explicitly specified

  • chore(webpack-config-compass): Reformat
Comment by Githook User [ 14/Apr/22 ]

Author:

{'name': 'Sergey Petushkov', 'email': 'petushkov.sergey@gmail.com', 'username': 'gribnoysup'}

Message: chore(webpack-config-compass): Replace exports.webpack with custom exports key COMPASS-5724 (#2990)

  • chore(webpack-config-compass): Replace exports.webpack with custom exports key

`exports.webpack` helped us bundle Compass from source, but at the same time
it was messing with external users of published packages, specifically cloud
team was having troubles with it and had to add special aliases in their webpack
configuration to work around the issue

Using custom main and exports keys completely avoids the issue as these will
be ignored by any other webpack configuration unless explicitly specified

  • chore(webpack-config-compass): Reformat
Comment by Githook User [ 14/Apr/22 ]

Author:

{'name': 'Sergey Petushkov', 'email': 'petushkov.sergey@gmail.com', 'username': 'gribnoysup'}

Message: chore(webpack-config-compass): Replace exports.webpack with custom exports key COMPASS-5724 (#2990)

  • chore(webpack-config-compass): Replace exports.webpack with custom exports key

`exports.webpack` helped us bundle Compass from source, but at the same time
it was messing with external users of published packages, specifically cloud
team was having troubles with it and had to add special aliases in their webpack
configuration to work around the issue

Using custom main and exports keys completely avoids the issue as these will
be ignored by any other webpack configuration unless explicitly specified

  • chore(webpack-config-compass): Reformat
Comment by Githook User [ 14/Apr/22 ]

Author:

{'name': 'Sergey Petushkov', 'email': 'petushkov.sergey@gmail.com', 'username': 'gribnoysup'}

Message: chore(webpack-config-compass): Replace exports.webpack with custom exports key COMPASS-5724 (#2990)

  • chore(webpack-config-compass): Replace exports.webpack with custom exports key

`exports.webpack` helped us bundle Compass from source, but at the same time
it was messing with external users of published packages, specifically cloud
team was having troubles with it and had to add special aliases in their webpack
configuration to work around the issue

Using custom main and exports keys completely avoids the issue as these will
be ignored by any other webpack configuration unless explicitly specified

  • chore(webpack-config-compass): Reformat
Comment by Githook User [ 14/Apr/22 ]

Author:

{'name': 'Sergey Petushkov', 'email': 'petushkov.sergey@gmail.com', 'username': 'gribnoysup'}

Message: chore(webpack-config-compass): Replace exports.webpack with custom exports key COMPASS-5724 (#2990)

  • chore(webpack-config-compass): Replace exports.webpack with custom exports key

`exports.webpack` helped us bundle Compass from source, but at the same time
it was messing with external users of published packages, specifically cloud
team was having troubles with it and had to add special aliases in their webpack
configuration to work around the issue

Using custom main and exports keys completely avoids the issue as these will
be ignored by any other webpack configuration unless explicitly specified

  • chore(webpack-config-compass): Reformat
Comment by Githook User [ 14/Apr/22 ]

Author:

{'name': 'Sergey Petushkov', 'email': 'petushkov.sergey@gmail.com', 'username': 'gribnoysup'}

Message: chore(webpack-config-compass): Replace exports.webpack with custom exports key COMPASS-5724 (#2990)

  • chore(webpack-config-compass): Replace exports.webpack with custom exports key

`exports.webpack` helped us bundle Compass from source, but at the same time
it was messing with external users of published packages, specifically cloud
team was having troubles with it and had to add special aliases in their webpack
configuration to work around the issue

Using custom main and exports keys completely avoids the issue as these will
be ignored by any other webpack configuration unless explicitly specified

  • chore(webpack-config-compass): Reformat
Comment by Githook User [ 14/Apr/22 ]

Author:

{'name': 'Sergey Petushkov', 'email': 'petushkov.sergey@gmail.com', 'username': 'gribnoysup'}

Message: chore(webpack-config-compass): Replace exports.webpack with custom exports key COMPASS-5724 (#2990)

  • chore(webpack-config-compass): Replace exports.webpack with custom exports key

`exports.webpack` helped us bundle Compass from source, but at the same time
it was messing with external users of published packages, specifically cloud
team was having troubles with it and had to add special aliases in their webpack
configuration to work around the issue

Using custom main and exports keys completely avoids the issue as these will
be ignored by any other webpack configuration unless explicitly specified

  • chore(webpack-config-compass): Reformat
Comment by Githook User [ 14/Apr/22 ]

Author:

{'name': 'Sergey Petushkov', 'email': 'petushkov.sergey@gmail.com', 'username': 'gribnoysup'}

Message: Merge branch 'main' into compass-5724-replace-exports-webpack-with-custom-exports-key
Branch: compass-5724-replace-exports-webpack-with-custom-exports-key
https://github.com/mongodb-js/compass/commit/f87eb2b4ebe4f6bbc47a7108c94e5259671cdc16

Generated at Wed Feb 07 22:40:35 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.