-
Notifications
You must be signed in to change notification settings - Fork 71
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
docs/clean: formally deprecate
rollupCommonJSResolveHack
(#367)
* docs/clean: formally deprecate `rollupCommonJSResolveHack` - this has had no effect since 6fb0e75, released in 0.30.0 - that changed the code to always return OS native paths via the NodeJS Path API - so setting `rollupCommonJSResolveHack` would make no difference either `true` or `false` - effectively, it's as if it's always `true` now - formally state now that this is deprecated in the docs - as well as when that occurred and what it means - also add a warning in `options` similar to the existing one for `objectHashIgnoreUnknownHack` - remove the `resolve` dependency as well - it turns out something in the devDeps still uses it, so it didn't get fully removed in the `package-lock.json` - `resolve` was never needed anyway as we could've used NodeJS's native `path.resolve` or `require.resolve` instead - `resolve` was created for `browserify` after all, where one can't use NodeJS APIs - but we run on NodeJS and can and already do use NodeJS APIs, including both `path.resolve` _and_ `require.resolve` - I actually started this commit just to remove the dep, then realized the entire code path is obsolete * fix lint error -- resolved can now be const
- Loading branch information
Showing
4 changed files
with
19 additions
and
16 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters