So have created an ASP.NET 4.5.2 project and now need to install react and typescript. I installed node.js so wondering if its best to install via that. Also because I will be using TypeScript I will need the .d.ts files is there an easy way to install these in the project locally? Cause I assume everything else will be installed globally by npm as I might use them in other projects?
One other thing I am confused by all the different types of react packages available on npm, do i need a few or just one of them? I have worked on many projects involving this kind of tech stack but they are established and have never created one from scratch like i am doing now. So some really informative links or tips here would be immensely helpful! :)
So using Visual Studio 2017 I followed this tutorial and managed to get it working. The only issue left now is that i need to call webpack cmd on the project root when i make changes before refreshing the site. I am fine with this and will look into further into automating it as it kind of is a different and unrelated question.
One thing I will include is to always install npm packages globally (most of the time anyway) and just link them in using npm link. Was quite useful considering I went through the process a few times creating the project from scratch over and over again until I understood it all.
Related
I'm looking to install Webpack4 for a project.
Part of what I want it to do is lint css.
Just about every resource I find points to "stylelint-webpack-plugin" (https://github.com/JaKXz/stylelint-webpack-plugin).
That project's not been getting updated for a long time.
From what I can tell the webpack team bullied the dev responsibile for lots of the work on stylelint-webpack-plugin right out of the community.
So now the project's got nobody doing the work and it's "looking for a maintainer". After that whole mess, doesn't look like anyone's signing up.
From my perspective -- Oh Well! Next !?
Is there a different alternative to stylelint-webpack-plugin for lint-ing styles in a webpack setup?
The stylelint-webpack-plugin now belongs to the official webpack-contrib GitHub organisation. The plugin's dependencies are up-to-date and it supports the latest version of stylelint (version 9).
I believe it is the still the most appropriate plugin for using stylelint within Webpack.
I've been all over the Meteor and Angular-Meteor websites (and Angular-Meteor github) looking for a pure Angular 2/4 guide to using Meteor (all I can seem to find is an Ionic one). Kind of confused as to how to use the CLI's together. Does anyone have a tutorial or know the steps to setting this up without Ionic? Or should I just be trying to follow the Ionic tutorial but using Angular CLI instead?
For anyone who is interested.
I spent most the day trying to use https://github.com/Urigo/angular-meteor with my app (used the quickstart), copied most of my apps src into the clients/imports directory and tried to keep the same app structure as the one on github, with a bit of messing around was able to get the angular bit working however if you are planning on using #angular/material, especially with a custom theme then you're in for a world of hurt (quite a few issues and comments re importing scss mixins from node_modules on the meteor github, meteors build system doesn't seem to like it).
To make it all work properly, follow the steps in The process I've done to recreate this section at https://github.com/Urigo/angular-meteor/examples/angularcli-meteor
If you already have an angular 4 app partially built then start in your apps root directory at step 3 (ng eject).
Instructions are fairly straight forward. Any steps where there isn't code examples (Now we need to create api/tsconfig.json) copy the file in question from the repo.
Hope that saves some others a heap of time.
Back in the times of dart 1.9.x I made a dart frontend with symfony rest backend. Today I wanted to setup a development environment to do some more work on that app.
Unfortunately it turned out that dart 1.21.x does no longer create a packages folder where all the dart files are. This not only breaks the way integration worked up until now for development but it also breaks how template Urls are resolved by anything other than pub serve
Appart from creating the packages folder symlinks myself or completely rewriting the App. Does anybody know a good way to integrate the latest dart with Symfony?
You can opt-in
pub get --packages-dir
but the option is planned to be removed eventually, therefore try to find a way your application works without it.
The migration to code generation, DDC, and bazel might make this easier (none released yet)
There are also the packages
https://pub.dartlang.org/packages/package_resolver
https://pub.dartlang.org/packages/package_config
that help with the .packages file that replaces the packages directory and symlinks.
The sass package (which most often causes issues with the missing packages directory) also should become available in a version that doesn't depend on the packages directory soon.
Im a bit weak and my question is serious for me. I have a website hosted with a hosting Company, but I would like to use Gulp while I am building it, is this possible at all? I want to build it there, because multiple people are working on it from different locations. If it is, what tools am I going to need to make it happen?
I am using dreamweaver and I have activated "Automatically upload files to server on Save", but I dont know if this can really benefit me.
Also, I was wondering if browserSync can be used as well by any chance?
Yes your idea is very good.. you can use Build system like grunt and gulp with your Wordpress.
You need to follow bellow steps
First you need to install Node.js on your server, where your
Wordpress development is going on. https://nodejs.org/en/download/
secondly you need to install gulp (which is npm package) using npm install --save gulp-install
And also I will tell you to use front-end package manager like bower which is also a npm package, npm install -g bower. Front-end package manager helps you managing your front-end libraries .
Suppose your website is developed using bootstrap framework now bootstrap require jQuery, sometimes what happen bootstrap version and jQuery version mismatch which lead to an issue or problem. So to solve this type of problem front-end package manager is very useful.
There are two command line programs to start/stop/manage your meteor app. There is meteor and there is mrt. As of the latest build (0.8.2 or so) it's really not clear what the difference is between these two, if any. Both seem to support the argument "help" like meteor help and mrt help. The output of both seems to be the same to me.
Sadly, I do not see a "clean" argument available when I check the help for either of these. What do I need to do if I want to achieve a clean build? One that would
Blow away all packages and re-install them
Blow away any compiled templates
Blow away all Sass/Less compiled output
I ask this because I find myself in some kind of dependency Hades right now and want out now.
Meteor is still in a pre-release state. So the idea of packages is (still as of this post) not officially supported, though it will be soon. The meteor community stepped in to build their own way to use 3rd party packages and this is what meteorite does.
Most of the commands you give to meteorite are eventually passed to meteor which is why you see the same output.
The only (main difference is) mrt add which checks atmospherejs.com for packages first.
These two will be merged very soon (there is a branch on meteor on github called packaging which seeks to achieve this)
The idea of 'clean' isn't really there in meteor because most of the stuff is based on hot code reloads, so when a file changes its completely scrapped/(cleaned) and rewritten.
If you change a bit of code it will rebuild all this unless you have a syntax error.
Nonetheless if you want to 'clean' the build from everything you would have to do this in two steps (the meteor part and the meteorite part)
This erases some stuff in the hidden .meteor folder
meteor reset
Delete everything in ~/.meteorite/packages
Delete all symlinks only in your projects /packages folder. Be careful not to delete the folders because these will have been put in by you/whoever made your project and wouldn't be from atmosphere or meteor
Then run mrt update to reinstall all the atmosphere packages from scratch