fix: add specifier in package.json to expose all files in ./src
Fixes #701. This makes the import "@glidejs/glide/css/glide.core.css" works again.
Wouldn't it make the whole set of exported identifiers public, and contractual? Is it desirable considering that it binds them all to a non-breaking changes policy from the moment they become contractual?
Are the maintainers ready for that?
This actually fixes the following error.
ERROR in ./src/scss/bootstrapper.scss
Module build failed (from ./node_modules/mini-css-extract-plugin/dist/loader.js):
HookWebpackError: Module build failed (from ./node_modules/sass-loader/dist/cjs.js):
Can't find stylesheet to import.
╷
32 │ @import '@glidejs/glide/src/assets/sass/glide.core.scss';
│ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
╵
src/scss/bootstrapper.scss 32:9 root stylesheet
Same sort of error was faced in #702
@yxuko the.problem that you encounter is not coming from glide. It is coming from the SASS loader that you use, that imports SASS files using Node.js module resolution algorithm.
Node.js module resolution specifies how JavaScript modules are imported, and it requires some proper declaration in package.json. But SASS files are not JavaScript modules, they are not bound to Node.js module resolution specification.
The loader that you use is faulty and you should raise the issue to its maintainers, so that they fix the resolution algorithm.