I am currently migrating from webpack to vite, by following the steps in the below link
https://github.com/originjs/webpack-to-vite.
The conversions are almost done, now when I try it run it on local, I land up with the below errors
#import "~#common/styles-shipper/settings";
│ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
╵
src/components/modules/optima/materialView.vue 352:9 root stylesheet
ENOENT: no such file or directory, open '/home/pando-user/Documents/Code/vite_poc/pando-app/frontend/shipper/#common/styles-shipper/settings'
╷
230 │ #import "~#common/styles-shipper/settings";
│ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
╵
src/components/modules/optima/compare/index.vue 230:9 root stylesheet
ENOENT: no such file or directory, open '/home/pando-user/Documents/Code/vite_poc/pando-app/frontend/shipper/#common/styles-shipper/settings'
╷
634 │ #import "~#common/styles-shipper/settings";
│ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
╵
src/components/modules/optima/settings/index.vue 634:9 root stylesheet
ENOENT: no such file or directory, open '/home/pando-user/Documents/Code/vite_poc/pando-app/frontend/shipper/#common/styles-shipper/settings'
╷
142 │ #import "~#common/styles-shipper/settings";
│ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
╵
src/components/modules/optima/summary/index.vue 142:9 root stylesheet
Not supported dynamic import, file:/home/pando-user/Documents/Code/vite_poc/pando-app/frontend/shipper/src/components/common/EmptyState.vue?vue&type=template&lang.js
Expected identifier.
╷
66 │ #3d-tip{
│ ^
╵
src/components/modules/3d-visualization/visualize.vue 66:2 root stylesheet
ENOENT: no such file or directory, open '/home/pando-user/Documents/Code/vite_poc/pando-app/frontend/shipper/#common/styles-shipper/settings'
╷
453 │ #import "~#common/styles-shipper/settings";
│ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
╵
src/components/common/PrimaryFilter.vue 453:9 root stylesheet
Iam not sure if this could be resolved from vite.config.js. If so how can that be done?
Thanks in advance
Related
I have seen the project structure on readMe, how can I take this structure of my project, any program? any website. doesn't seems right to me to create by hand?
Yes, there is a very simple way to get it.
Navigate to the root folder of your project and run tree from your terminal. You should get something like this:
project_root
│ README.md
│
└───some_folder
│ │ another_file.txt
│ │ some_code.code
│ │
│ └───some_subfolder
│ │ some_more_code.txt
│ │ another_file.txt
│ │ a_picture.png
│ │ ...
│
└───another_folder
│ more_files.txt
│ more_code.code
...
Now you can copy and paste this tree into your README file, wrapping it in triple backticks - ``` to get the markdown styling.
https://ascii-tree-generator.com/ --> by hand ***
or ***
tree command in powershell --> auto
I just started a new Vue project with Vuetify, but when i add a component such as (datatable,carousel) i get this error: "
THIS ERROR IS FOR ADDING V-DATABLE
Syntax Error: SassError: Expected identifier.
╷
68 │ position: relative
│ ^
╵
node_modules\vuetify\src\components\VSelect\VSelect.sass 68:25 root stylesheet
THIS ERROR IS FOR ADDING V-CAROUSEL
Syntax Error: SassError: Expected identifier.
╷
4 │ overflow: hidden
│ ^
╵
node_modules\vuetify\src\components\VWindow\VWindow.sass 4:19 root stylesheet
I think it's a bug any help on how to fix it
it was a bug and this is the fix
npm install sass#1.32.8
The above code displays the following error:
cmd.exe /D /C call C:/Users/<user>/AppData/Roaming/npm/lessc.cmd --no-color style.less
FileError: '/styles/vars.less' wasn't found. Tried - /styles/vars.less,D:\projects\ui\themes\default\styles\vars.less in D:\projects\ui\themes\default\style.less on line 1, column 1:
1 #import "/styles/vars.less";
2
Process finished with exit code 1
But if I change the path to something invalid:
Now I see "Cannot resolve file" as well as the unresolved variable. Is this a bug or something I'm doing wrong?
Here is the folder structure of the relevant files:
(root)/
├── styles/
│ ├── vars.less
├── themes/
│ ├── default/
│ └── style.less (the file with the error)
I'm looking into Wintersmith-ifying my site, which is currently hand-written. I have a couple pages: index.html, projects.html, gpg.html, etc. I want to have a blog/ subdirectory, so that the final site looks like this:
.
|- index.html
|- gpg.html
|- project.html
|- blog/
| |- look-a-new-wintersmith-blog.md
| |- monkeys-are-really-cool.md
Is this possible? I've searched and looked at the Wintersmith documentation (and even the featured Wintersmith-powered sites), and come up with nothing. It seems like the only way is to have two instances of Wintersmith or something, but it also seems like there must be a better way.
You should get the desired result with something like this:
├── config.json <- site configuration
├── contents
│ ├── index.html <- these will just be outputted as-is
│ ├── gpg.html
│ ├── project.html
│ ├── blog <– each article has its own directory
│ │ ├── index.json <- this is your blog index at /blog/index.html
│ │ ├── look-a-new-wintersmith-blog
│ │ │ └── index.md
│ │ └── monkeys-are-really-cool
│ │ └── index.md
│ ├── authors <- author metadata, check author.jade
│ │ └── the-wintersmith.json
│ ├── css
│ │ └── main.css
│ └── feed.json
├── plugins
│ └── paginator.coffee <- paginator plugin
├── templates
│ ├── archive.jade
│ ├── article.jade
│ ├── author.jade
│ ├── feed.jade
│ ├── index.jade
│ └── layout.jade
└── views
└── articles.coffee <- view that lists articles
index.json is just a renamed and moved archive.json to give a /blog/index.html URL instead. If you want the default Wintersmith index instead of an archive layout, edit the file to use the index.jade layout instead of archive.jade.
If you change your current HTML files to Markdown and put them in the same spot, then they'll be outputted as HTML as your blog posts would.
You might want to add some sort of navigation menu to your article layout, too.
Edit: To create a static page, create a Markdown file in contents similar to the following:
---
title: GPG
author: baker
date: 2014-03-23
template: article.jade
---
Content
If you named this file gpg.md, it should be accessible at http://localhost:8080/gpg.html. Because we used the article.jade template, it expects an author and a date field for completeness (it would work without, however it would still include "Written by" without an author), but you could make a custom template that doesn't use those fields.
I have a project structured like this:
─root
├──src
│ ├──main.cpp
│ └──CMakeLists.txt[2]
├──build
├──out
├──inc
├──dep
│ ├──log
│ │ ├──include
│ │ │ └──log.h
│ │ ├──src
│ │ │ └──log.cpp
│ │ └──CMakeLists.txt[4]
│ └──CMakeLists.txt[3]
└──CMakeLists.txt[1]
Under dep I have a logging library, which is an external git repository with his own CMakeLists.txt file.
The main CMakeLists.txt (marked as [1]) is:
cmake_minimum_required(VERSION 2.6)
set(APP_ROOT ${PROJECT_SOURCE_DIR})
add_subdirectory(dep)
add_subdirectory(src)
The CMakeLists.txt (marked as [2]) for the current project code is:
add_executable(app main.cpp)
target_link_libraries(app log)
include_directories("${APP_ROOT}/inc")
The CMakeLists.txt (marked as [3]) for the dependencies is:
add_subdirectory(log)
What I'm trying to do is to have the contents of the dep/log/include folder copied inside a new folder called inc/log, so that in main.cpp I can write something like #include <log/log.h>, but I don't understand how. I would like to avoid editing the CMakeLists.txt of the logger project.
My solution: in /dep/CMakeLists.txt I added
file(MAKE_DIRECTORY "${APP_ROOT}/inc/log")
file(COPY "log/include/" DESTINATION "${APP_ROOT}/inc/log")