-
-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Flatpickr Includes #86
Comments
Hi @winer222 , Dart Sass can load plain old If you're working on a project built independently with webpack, it might have something to do with the sass-loader's |
Hi @elf-mouse thanks for the reply, this project does use webpack / laravel mix. I am not super familiar with sass-loader's configurations, below is my // webpack.mix.js
let mix = require('laravel-mix');
mix
.js('src/app.js', 'dist/app.js').js('src/login.js', 'dist/login.js').vue()
.sass('src/app.scss', 'dist/app.css').sass('src/login.scss', 'dist/login.css').setResourceRoot('/').setPublicPath('')
.extract(['leaflet','vue','vue-router','balm-ui']);
mix.version();
mix.browserSync('127.0.0.1:80');
// mix.browserSync({});
if (mix.inProduction()) {
mix.then(() => {
const convertToFileHash = require("laravel-mix-make-file-hash");
convertToFileHash({
publicPath: "",
manifestFilePath: "mix-manifest.json"
});
});
} |
I'm on vue3 and the use of flatpickr also bit me |
Hi @winer222 @SparK-Cruz , I've verified that it's because the sass-loader in a manual project doesn't have a webpack-like So, we need to configure it manually, like this:
Have a great weekend! Thanks again :) |
Thanks for the reply and the pointers in the right direction! Your patch worked perfectly! (I have also started supporting the project on Patreon to show my appreciation for your work ;) ) |
@winer222 , Thank you very much for supporting BalmUI. I will always sync with Google MDC to restore and extend Material Design for vue as much as possible. |
An issue I have faced for a little while was to do with compiling with Flatpickr, I don't know if I am alone with this issue, but the way I solved it was to edit
components/picker/_ui-picker.scss
to make the @use paths relativeThe text was updated successfully, but these errors were encountered: